Avoid duplication in generated community modules rules.mk

[zvecr]

Description

Due to the way the content was previously generated, the moving of module config to slightly later does not change the effective order.

Also avoids the scenario where keymap.json "keyboard` field has a different value to the currently comping keyboard. This can happen when a keymap is shared across multiple revisions (or just set to a completely incorrect value).

keyboards/test/rev1/keyboard.json - include module A
keyboards/test/rev2/keyboard.json - include module B
keyboards/test/keymaps/default/keymap.json - include module C sets keyboard field to "test/rev1"

If you then compile test/rev2:default it will incorrectly pull in modules A, B and C

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout (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).