Auth Unification, Custom Auths, better tests

[Ansonhkg]

Description

This PR introduces Tinny, an improved mini e2e testing framework that allows us to write tests in TypeScript. It leverages esbuild for rapid test compilation and execution. Tinny includes typed test helper functions to generate new identities within tests, and provides APIs to modify the development environment.

See docs:
https://github.com/LIT-Protocol/js-sdk/tree/feature/lit-2958-auth-unification-ts-tests/local-tests

Note

We are not merging this PR to master until all related PRs are merged to this branch.

• feat(endpoints): centralised all endpoints with types #438
• Feature/lit 3017 auth unification migrate actual tests #440
• fix(sessionKey): signed session key mismatch with the one being signe… #439
• Feature/lit 2962 auth unification better siwe authsig creation #436

Cherry Picked:

• Feature/lit 3041 js sdk cherry pick fixes for session key mismatch 443#issuecomment 2082614246 #446

We should also raise a PR to remove all existing V0 features when we are ready to deploy. They are now being tracked here

Changes

• Local Network Context: Fixed issues to ensure local network settings are accurately recognized during test runs.
• Helper Functions: Introduced new helper functions for siweMessage creation and authSig crafting, addressing circular dependencies in the auth-helpers package.
• Fetch Polyfill: Implemented a temporary fix to ensure the fetch API is polyfilled correctly when bundling the tests.
• Interface Updates: Restored the litNodeClient to the ILitNodeClient interface to ensure type consistency.
• Auth unification params: Expanded authNeededCallbacks to support additional parameters and introduced a - higher-level function, getPkpSessionSigs, to streamline PKP sessionSigs creation process.
• Type Migration: Migrated type definitions to the types package to enhance modularity and maintenance.

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)
• This change requires a documentation update

How Has This Been Tested?

Screen.Recording.2024-04-23.at.23.26.00.mov

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[joshLong145]

Left some comments going to do another pass