Fix LightningCLI signature parameter resolving for some lightning classes

[mauvilsa]

What does this PR do?

Uses a new version of jsonargparse that extended the support for **kwargs to properly find signature parameters where possible by inspecting the source code, see omni-us/jsonargparse#114 (comment). The relevant documentation is at https://jsonargparse.readthedocs.io/en/latest/#parameter-resolvers.

Fixes #11653
Fixes #12697
Fixes #11574
Fixes #8561
Fixes #9887 (comment)
Fixes #8008 (comment)

Does your PR introduce any breaking changes? If yes, please list them.

None

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• [n/a] Did you make sure to update the documentation with your changes? (if necessary)
• Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you list all the breaking changes introduced by this pull request?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

[mauvilsa]

The jsonargparse version is 4.10.0.dev2 because from feedback here it might make sense to change things before a final release. Though the idea is that this pull request is merged only when 4.10.0 is out.