Chaining OSL and MO

[DavidSannier]

Description

Make it possible to chain One Shot Layer and Momentary Layer or another One Shot Layer
When a one shot layer is active and a key other than a modifier is pressed, the one shot layer is cleared
and the release of this key is reported just before returning fromprocess_action
This release is surrounded by layer_on(get_oneshot_layer()) and layer_off(get_oneshot_layer())
It works well for regular keys, but for layer switching, it turns off the requested layer prematurely
Resetting do_release_oneshot in this case will avoid this behavior

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[github-actions]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[github-actions]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[github-actions]

Thank you for your contribution!
This pull request has been automatically closed because it has not had activity in the last 30 days. Please feel free to give a status update now, ping for review, or re-open when it's ready.
// [stale-action-closed]

[DavidSannier]

@tzarc, this PR was flagged 'breaking_change_2024q3', 'breaking_change_2024q4', but then 'stale' before getting merged.
Do I need to open another one ?

[tzarc]

I honestly don't know why this wasn't looked at -- usually we ignore PRs which have merge conflicts or other issues because it's up to the PR submitter to keep things updated... but that's not the case here.

I'll flag it with the rest of the team for review.