ref(project-creation): Extract a useIssueAlertNotificationOptions hook

Pull the shared shell out of IssueAlertNotificationOptions into a useIssueAlertNotificationOptions hook: the shouldRenderNotificationConfigs derivation, the setup-button impression analytics, and the querySuccess gate. The SCM layout can reuse the same logic and analytics instead of duplicating them. The classic component consumes the hook and renders identically.

Author: jaydgoss

static/app/views/projectInstall/issueAlertNotificationOptions.tsx

@@ -249,11 +249,19 @@ export function useCreateNotificationAction({
   };
 }
 
-export function IssueAlertNotificationOptions(
-  notificationProps: IssueAlertNotificationProps
-) {
-  const {actions, setActions, querySuccess, shouldRenderSetupButton} = notificationProps;
-
+/**
+ * Shared shell for the project-creation notification options: derives which
+ * sub-controls to show and reports the setup-button impression. The classic
+ * (`IssueAlertNotificationOptions`) and SCM (`ScmIssueAlertNotificationOptions`)
+ * layouts reuse this and differ only in presentation.
+ *
+ * @public Consumed by the SCM layout in a downstream PR.
+ */
+export function useIssueAlertNotificationOptions({
+  actions,
+  querySuccess,
+  shouldRenderSetupButton,
+}: IssueAlertNotificationProps) {
   const shouldRenderNotificationConfigs = actions.some(
     v => v !== MultipleCheckboxOptions.EMAIL
   );
@@ -262,6 +270,20 @@ export function IssueAlertNotificationOptions(
     setup_message_integration_button_shown: shouldRenderSetupButton,
   });
 
+  return {
+    querySuccess,
+    shouldRenderNotificationConfigs,
+    shouldRenderSetupButton,
+  };
+}
+
+export function IssueAlertNotificationOptions(
+  notificationProps: IssueAlertNotificationProps
+) {
+  const {actions, setActions} = notificationProps;
+  const {querySuccess, shouldRenderNotificationConfigs, shouldRenderSetupButton} =
+    useIssueAlertNotificationOptions(notificationProps);
+
   if (!querySuccess) {
     return null;
   }