chore(deps): update deps to latest, drop old beachball and eslint deps, add new eslint config file

[ctran88]

What's New?

• update deps to latest
  • except node-fetch, which causes some import issues in v3
• since eslint was updated from v8 to v9, had to update config file and rules
• moved the old e2e tests to be co-located next to their source files since eslint was complaining that it wasn't a part of the project service discovery
• dropped beachball

Screenshots (if appropriate):

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have manually tested my code thoroughly
• I have added/updated inline documentation for public facing interfaces if relevant
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing integration and unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Additional context

[bertrmz]

Does the data in this file need to be persisted in a different format?

[ctran88]

no the last published version already used the contents of this file, which is put into CHANGELOG.md. this is only a cache for beachball

[bertrmz]

The other matchers here seem to be using constructors of primitive JS types.
What's the expected behavior of an expect.any(Array<FooType>) match?

[ctran88]

it matches against an array of objects whose shape (keys and key value types) conform to FooType

[bertrmz]

Does the case of an undefined config need to be handled?

& a separate question, but why are accessToken and headers.Authorization both needed in this object?

[ctran88]

apiConfiguration is only ever called internally when constructing codegen options

passage-flex-node/src/classes/PassageFlex/PassageFlex.ts

Line 31 in 7dae6eb

apiConfiguration: apiConfiguration({

and we take in our own values in PassageFlexConfig to populate this function's parameters

passage-flex-node/src/classes/PassageFlex/types.ts

Line 4 in ceabe03

export type PassageFlexConfig = {

where we always throw on undefined for the api key before this function is called

passage-flex-node/src/classes/PassageFlex/PassageFlex.ts

Lines 23 to 24 in 7dae6eb

	if (!config.apiKey) {
	throw Error('A Passage API key is required. Please include {appId: YOUR_APP_ID, apiKey: YOUR_APP_ID}.');

so the value should never be undefined at this point. i changed the parameter to be required in 9b6211c

[ctran88]

why are accessToken and headers.Authorization both needed in this object?

good point, i've removed the header in de63778