Please address the comments from this code review:

## Overall Comments
- The Angular package updates currently bump core packages to v19 but leave @angular/cdk at v15; please align all Angular dependencies to the same major version to prevent compatibility issues.
- There are many manual formatting tweaks across templates and code; consider running the official Angular upgrade schematics and using Prettier/ESLint auto-formatting to ensure consistent styling and reduce manual overhead.
- You've added 'standalone: false' to almost every component; consider auditing these and migrating eligible components to standalone: true or removing redundant standalone flags to leverage Angular 19's standalone component feature.

## Individual Comments

### Comment 1
<location> `packages/altair-app/src/app/modules/altair/services/gql/oldBuildClientSchema.ts:165-168` </location>
<code_context>

</code_context>

<issue_to_address>
**issue (code-quality):** Avoid function declarations, favouring function assignment expressions, inside blocks. ([`avoid-function-declarations-in-blocks`](https://docs.sourcery.ai/Reference/Rules-and-In-Line-Suggestions/TypeScript/Default-Rules/avoid-function-declarations-in-blocks))

<details><summary>Explanation</summary>Function declarations may be hoisted in Javascript, but the behaviour is inconsistent between browsers.
Hoisting is generally confusing and should be avoided. Rather than using function declarations inside blocks, you
should use function expressions, which create functions in-scope.
</details>
</issue_to_address>

### Comment 2
<location> `packages/altair-app/src/app/modules/altair/services/gql/oldBuildClientSchema.ts:353-355` </location>
<code_context>
          !('onField' in directiveIntrospection && directiveIntrospection.onField)
            ? []
            : [DirectiveLocation.FIELD],

</code_context>

<issue_to_address>
**suggestion (code-quality):** Invert ternary operator to remove negation ([`invert-ternary`](https://docs.sourcery.ai/Reference/Rules-and-In-Line-Suggestions/TypeScript/Default-Rules/invert-ternary))

```suggestion
          'onField' in directiveIntrospection && directiveIntrospection.onField ? [DirectiveLocation.FIELD] : [],

```

<br/><details><summary>Explanation</summary>Negated conditions are more difficult to read than positive ones, so it is best
to avoid them where we can. By inverting the ternary condition and swapping the
expressions we can simplify the code.
</details>
</issue_to_address>

### Comment 3
<location> `packages/altair-app/src/app/modules/altair/store/async-storage-sync.ts:423-431` </location>
<code_context>
      if (action.type === APP_INIT_ACTION) {
        if (action.payload?.initialState) {
          nextState = defaultMergeReducer(
            nextState,
            (action as AppInitAction).payload.initialState,
            action
          );
        }
      }

</code_context>

<issue_to_address>
**suggestion (code-quality):** Merge nested if conditions ([`merge-nested-ifs`](https://docs.sourcery.ai/Reference/Rules-and-In-Line-Suggestions/TypeScript/Default-Rules/merge-nested-ifs))

```suggestion
      if (action.type === APP_INIT_ACTION && action.payload?.initialState) {
            nextState = defaultMergeReducer(
              nextState,
              (action as AppInitAction).payload.initialState,
              action
            );
      }

```

<br/><details><summary>Explanation</summary>Reading deeply nested conditional code is confusing, since you have to keep track of which
conditions relate to which levels. We therefore strive to reduce nesting where
possible, and the situation where two `if` conditions can be combined using
`and` is an easy win.
</details>
</issue_to_address>