Resolve info.json/rules.mk feature conflicts in three boards

[fauxpark]

Description

⚠ 0_sixty/underglow: Feature rgblight is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ handwired/reclined: Feature bootmagic is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ handwired/reclined: Feature mousekey is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ handwired/reclined: Feature extrakey is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ handwired/reclined: Feature console is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ handwired/reclined: Feature command is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ handwired/reclined: Feature nkro is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ handwired/reclined: Feature backlight is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ handwired/reclined: Feature audio is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ makenova/omega/omega4: Feature bootmagic is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ makenova/omega/omega4: Feature mousekey is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ makenova/omega/omega4: Feature extrakey is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ makenova/omega/omega4: Feature console is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ makenova/omega/omega4: Feature command is specified in both info.json and rules.mk, the rules.mk value wins.
⚠ makenova/omega/omega4: Feature nkro is specified in both info.json and rules.mk, the rules.mk value wins.

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