Feature/lit 3269 js sdknode fix custom auth issue

[Ansonhkg]

Description

This PR addresses a few issues:

1. Unable to mint pkp with custom auth using mintWithAuth because the function is throwing an error when getting authId from Lit supported auth methods.
2. Not passing the whole set of params back to authNeededCallback when resign is required
3. jsParams type not accepting any other keys

New feature:

• Add getLitActionSessionSigs() with explicit interface properties (either litActionCode or litActionIpfsId, and required jsParams).

Related PRs:

• https://github.com/LIT-Protocol/lit-assets/pull/1157
• https://github.com/LIT-Protocol/lit-assets/pull/1158
• developer guide: https://github.com/LIT-Protocol/developer-guides-code/pull/13

Type of change

• [x] Bug fix (non-breaking change which fixes an issue)
• [x] 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?

Test Command:

DEBUG=true NETWORK=localchain yarn test:local --filter=testUseCustomAuthSessionSigsToPkpSign

✅ res: {
  r: '4605d1450c67301575e0306b89b1ce6a68548b720e785820cc7ca6f835c858ab',
  s: '2e8558d89f69a2b37296a510721698c8989a0b5c1df58eb74a0b960f9683860e',
  recid: 0,
  signature: '0x4605d1450c67301575e0306b89b1ce6a68548b720e785820cc7ca6f835c858ab2e8558d89f69a2b37296a510721698c8989a0b5c1df58eb74a0b960f9683860e1b',
  publicKey: '04F7CD6AA4977DB70C87D615F9E9F6660A30FB979AD7E4858AED7D9EBECF8A39D66C23916286990A121A406FF534DD1A5087B3AFD6E8BD35A31EB858387C0C2389',
  dataSigned: '7D87C5EA75F7378BB701E404C50639161AF3EFF66293E9F375B5F17EB50476F4'
}

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