session.ts defined isAngularCore, isExternalAngularCore, and isInternalAngularCore as byte-identical copies of the already-exported versions in utils.ts. Only isAngularCore was used locally; the other two were dead. handlers/template_info.ts already imports the utils version. Remove the duplicates and import isAngularCore from utils.

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/main/contributing-docs/commit-message-guidelines.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.dev application / infrastructure changes
• Other... Please describe:

What is the current behavior?

vscode-ng-language-service/server/src/session.ts declares three local helpers (isAngularCore, isExternalAngularCore, isInternalAngularCore) that are byte-for-byte identical to the exported versions in vscode-ng-language-service/server/src/utils.ts. Only isAngularCore is referenced inside session.ts; the other two exist solely to support that local copy. handlers/template_info.ts already consumes the utils version, so the project ships two copies of the same logic.

What is the new behavior?

session.ts imports isAngularCore from ./utils and the three local helpers are removed. Behavior is unchanged. The server unit tests (//vscode-ng-language-service/server/src/tests:test) and the LSP integration suite (//vscode-ng-language-service/integration/lsp:test) both pass.

Does this PR introduce a breaking change?

• Yes
• No