Update DZ60 Files & Features

[aggynium]

Description

• Added layouts/community/60_ansi_arrow/aggynium/keymap.c
• Added layouts/community/60_ansi_arrow/aggynium/readme.md
• Added layouts/community/60_ansi_arrow/aggynium/rules.mk
• Added RGB Lighting/LED/Underglow as Caps Lock, Num Lock, Scroll Lock, and Layer Indicator to keyboards/dz60/keymaps/60_plus_arrows/keymap.c
• Added RGB Lighting/LED/Underglow as Caps Lock, Num Lock, Scroll Lock, and Layer Indicator to layouts/default/60_ansi_arrow/default_60_ansi_arrow/keymap.c

Types of Changes

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

Issues Fixed or Closed by This PR

• None

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.
• [x] I have read the CONTRIBUTING document.
• [x] I have added tests to cover my changes.
• [x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[fauxpark]

Unfortunately QMK has changed its stance on accepting user keymaps to the repository.

qmk/qmk_firmware is no longer accepting PRs for keymaps other than for manufacturer-supported keymaps. User keymap workflow has been documented here for several years. This change is to progressively reduce the maintenance burden on the project, and to allow us to focus on the core features of QMK.

QMK Firmware now officially supports storing user keymaps outside of the normal QMK Firmware repository, allowing users to maintain their own keymaps without having to fork, modify, and maintain a copy of QMK Firmware themselves.

While we appreciate the time that was taken on this PR, hopefully you understand we are closing it, so that QMK can improve in the long term.