Allow the exclusions of key presses to not actuate the haptic feedback

[darkcruix]

Description

With the entry of HAPTIC_EXCLUSION_KEYS 1 in config.h exclusion keys can be enabled.
By default they contain modifier and layer keys, which won't activate the haptic feedback, if set.
Additional keys can be added in config.h in a comma separated list in the form of:
#define HAPTIC_EXCLUSION_KEY_ADDITIONAL { KC_A, KC_B, KC_C }
In case it is desired to exclude only the self-defined and comma-separated list (without having the modifier and layer keys excluded), it can be achieved by turning off the default set in config.h:
#define HAPTIC_EXCLUSION_KEY_DEFAULT(keycode) 0

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).

[darkcruix]

corrected incorrect formatting

[purdeaandrei]

I am also interested in getting this change through.
I have tested this changeset with HAPTIC_ENABLE=SOLENOID, and works fine for me.
I don't have the hardware to test this with DRV2605L, but the code is generic, and I don't see why it wouldn't work.

[drashna]

This should be a define, not part of the rules.mk stuff.

Additionally, would rather a bool exclude_haptic_key(uint16_t, keyrecord_t *record) function for determining which keys to exclude or not, much like with how many of the other per key stuff works.

[darkcruix]

@drashna The requested changes have been implemented (function that determines the keys to exclude and removed the rules.mk portion).

[darkcruix]

@drashna Great recommendations! I have committed all changes and tested it against the haptic feedback against all option variations. Only change I'd suggest is to #define HAPTIC_EXCLUSION_KEY_DEFAULT(keycode, tapcount) for consistency in the documentation.

[darkcruix]

@drashna Huge thanks for the guidance. I have re-implemented it according the other areas. Tests have been run against all options with a Solenoid.

[drashna]

Could this target develop, actually?
(you can edit the title to change the targeted branch)

[drashna]

n/m, I've done it. And thanks!