feat(types): ship TypeScript definitions directly from the lock repo

[ankita10119]

Changes

The @types/auth0-lock package on DefinitelyTyped is significantly out of date (last updated for v11, current version is v14). Several constructor options introduced since then, forceAutoHeight, mobile, disableWarnings, preferConnectionDisplayName, useCustomPasswordlessConnection, emailFirst, connectionResolver, and hooks, were missing, causing TypeScript consumers to get compiler errors or fall back to any.

This PR ships type definitions directly from the lock repo by adding "types": "types/index.d.ts" to package.json. TypeScript resolves this automatically at install time, so no separate @types/ package is needed. The definitions include a type-level test file (types/auth0-lock-tests.ts) and a types/tsconfig.json for local validation.

Note on Version Compatibility / Fallback Behavior

The bundled types are scoped to v14+ only by the nature of npm versioning - no explicit version guard is needed in the code.

How it works:

npm install auth0-lock (v14) → consumer gets the package.json that contains "types": "types/index.d.ts". TypeScript reads this field automatically at install time and resolves the bundled definitions.

npm install auth0-lock@11 / @12 / @13 → those published tarballs have no "types" field and no types/ directory. TypeScript finds nothing bundled and falls back to @types/auth0-lock from DefinitelyTyped as before.

The boundary is purely physical - the types/ directory simply does not exist in older published versions on npm.

Side effect to be aware of: Once a user upgrades to v14, @types/auth0-lock is silently ignored in favour of the bundled types. If they had any local type augmentations or workarounds against @types/auth0-lock, those may stop working.

References

Resolves #2741

Testing

• This change adds unit test coverage
• This change adds integration test coverage
• This change has been tested on the latest version of the platform/language

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All code quality tools/guidelines have been run/followed
• All relevant assets have been compiled