Add mouse button bindings

[tomas7770]

Description

Adds support for binding mouse buttons to input actions, similar to existing implementation of keyboard/gamepad. Serialization functions are also implemented in order to support adding bindings in an asset.
Adds a new showcase to the input sample to test the bindings.

Checklist

• Self-review changes.
• Evaluate impact on the documentation.
• Ensure test coverage.
• Write new samples.

[github-actions]

PR Preview Action v1.4.4
Preview removed because the pull request was closed.
2023-11-19 11:04 UTC

[codecov]

Codecov Report

Attention: 22 lines in your changes are missing coverage. Please review.

Comparison is base (3f97f0e) 41.74% compared to head (dcc5cc0) 41.60%.

Files	Patch %	Lines
core/src/cubos/core/io/window.cpp	0.00%	22 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #792      +/-   ##
==========================================
- Coverage   41.74%   41.60%   -0.14%     
==========================================
  Files         108      108              
  Lines        6998     7020      +22     
==========================================
  Hits         2921     2921              
- Misses       4077     4099      +22     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[RiscadoA]

Thanks for working on this @tomas7770! LGTM, just needs some changes to the input sample's page before being merged :)

[RiscadoA]

Looks great! Ty! Just one thing before merging: some of your commit messages don't follow the format - you can use git rebase -i HEAD~7 to edit your previous 7 commits, and change each pick to reword (or just r) to change their messages. Most of your commits would fall under the feat(input) scope - for formatting one, you should use style: fix formatting. The commit you have which touches both sides, I would use feat(window) since its mostly window related code that's being changed. Usually when we can't choose a scope we try to split the commits into multiple ones or just omit the scope entirely.

Also, some tips for future PRs:

• you can press the 'auto merge' button to merge this automatically when all conversations are resolved and when the PR is approved.
• feel free to press the resolve button on reviews after pushing fixes for them.

[tomas7770]

Looks great! Ty! Just one thing before merging: some of your commit messages don't follow the format - you can use git rebase -i HEAD~7 to edit your previous 7 commits, and change each pick to reword (or just r) to change their messages. Most of your commits would fall under the feat(input) scope - for formatting one, you should use style: fix formatting. The commit you have which touches both sides, I would use feat(window) since its mostly window related code that's being changed. Usually when we can't choose a scope we try to split the commits into multiple ones or just omit the scope entirely.

Something like this?

feat(input): partially implement mouse button bindings
feat(window): add serialization for mouse buttons
fix(input): add mouse binds to input sample, to fix crash
feat(input): add mouse button showcase to input sample
style: fix formatting
feat(input): remove mouse for next-showcase in input sample
docs(input): add mouse showcase to input sample docs

[RiscadoA]

Looks great! Ty! Just one thing before merging: some of your commit messages don't follow the format - you can use git rebase -i HEAD~7 to edit your previous 7 commits, and change each pick to reword (or just r) to change their messages. Most of your commits would fall under the feat(input) scope - for formatting one, you should use style: fix formatting. The commit you have which touches both sides, I would use feat(window) since its mostly window related code that's being changed. Usually when we can't choose a scope we try to split the commits into multiple ones or just omit the scope entirely.

Something like this?

feat(input): partially implement mouse button bindings
feat(window): add serialization for mouse buttons
fix(input): add mouse binds to input sample, to fix crash
feat(input): add mouse button showcase to input sample
style: fix formatting
feat(input): remove mouse for next-showcase in input sample
docs(input): add mouse showcase to input sample docs

LGTM!