Replace deprectated importsNotUsedAsValues option with verbatimModuleSyntax

[m-akinc]

Pull Request

🤨 Rationale

The importsNotUsedAsValues TypeScript option is deprectated and will stop working in TypeScript 5.5. It is replaced by verbatimModuleSyntax.

My motivation for this change is that while updating Nimble to Angular 18, I found that importsNotUsedAsValues was forcing me to do a type-only import of Router and ActivatedRoute in router_link.ts. But doing so caused a different error for NimbleAnchorRouterLinkWithHrefDirective:

error NG2016: The directive NimbleAnchorRouterLinkWithHrefDirective inherits its constructor from RouterLink, but the latter has a constructor parameter that is not compatible with dependency injection. Either add an explicit constructor to NimbleAnchorRouterLinkWithHrefDirective or change RouterLink's constructor to use parameters that are valid for DI.

Both Router and ActivatedRoute are parameters to the RouterLink constructor. The problem is that if we do a type-only import of Router and ActivatedRoute, the compiler doesn't know that they are decorated to be injectable. Using verbatimModuleSyntax solves this by allowing us to import from the definition file rather than the type declaration file for those types, even though we're not directly using the definition.

This PR changes the option for the Angular projects, as well as nimble-components, spright-components, and storybook.

👩‍💻 Implementation

Had to update all imports of type symbols to explicitly say type.

🧪 Testing

Builds and existing tests pass.

✅ Checklist

• I have updated the project documentation to reflect my changes or determined no changes are needed.

[m-akinc]

@mollykreis will you buddy this change?

[rajsite]

PR is in draft and build is failing but I was reset. I'm assuming still in dev and I'm not reviewing yet but FYI in-case a review was expected.

[jattasNI]

I don't think you need to wait for any of the other code owners to submit this.

[m-akinc]

There were three tab scrolling tests failing in Webkit, but I suspect they must be intermittent. I've restarted the build, and I'll disable those tests in a separate PR, assuming my change isn't somehow responsible.