Move tap hold confs away from keyboard-level files

[precondition]

Description

This moves tap hold configuration settings like IGNORE_MOD_TAP_INTERRUPT
away from keyboard-level files and into the config.h files of the
default and via (it if exists) keymaps.

#define TAP_TERM x is ignored, but I can make a follow-up commit to move it away from keyboard-level files too.

The motivation for this PR is the following rule in the documentation on keyboard PRs:

• keyboard config.h
  • don't repeat MANUFACTURER in the PRODUCT value
  • no #define DESCRIPTION
  • no Magic Key Options, MIDI Options or HD44780 configuration
  • user preference configurable #defines need to be moved to keymap config.h
  • "DEBOUNCE" instead of "DEBOUNCING_DELAY"
  • bare minimum required code for a board to boot into QMK should be present
    • initialisation code for the matrix and critical devices
    • mirroring existing functionality of a commercial board (like custom keycodes and special animations etc.) should be handled through non-default keymaps
  • Vial-related files or changes will not be accepted, as they are not used by QMK firmware (no Vial-specific core code has been submitted or merged)

Personally speaking, the fact that Dactyl Manuform enables PERMISSIVE_HOLD by default tripped me up because I couldn't understand why my keyboard was acting in a PERMISSIVE_HOLD manner, and thus causing modifier misfires, despite not having enabled it in my keymap config.h.

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

[drashna]

Need a license header and an include guard.

Same with the rest of the config.h files

[precondition]

Whose name should I put in the license header though? The keyboard maker's? Mine?

[drashna]

If unsure, then just QMK is fine.

[stale]

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 awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[precondition]

I'm currently busy with uni exams but I will get back to this, this is not stale.

[precondition]

Will be in draft until #15741 gets merged.