Implementing Rebranding and Architectural Alignment

[mdwigley]

Description

This PR performs a full structural and semantic realignment of the project, transitioning from PlugHub to NucleusAF (Nucleus Application Framework).

It replaces plugin‑oriented terminology with module‑centric abstractions, reorganizes the solution into clearly defined architectural layers, formalizes extensibility patterns, introduces configuration accessors/handlers, and updates all tests, documentation, and build targets to match the new architecture.

Related Issue

• Resolves Rebrand and Architectural Alignment #140

Motivation and Context

The previous “plugin” terminology created conceptual ambiguity, implying optional extensions rather than core compositional units.

This alignment corrects the mental model, codifies previously implicit extensibility patterns, and establishes a stable architectural foundation for long‑term growth.

The licensing shift to MPL‑2.0 supports clearer boundaries for third‑party module authors.

How Has This Been Tested?

• All automated tests pass
• All smoke tests pass.
• All functionality tests pass.
• No regressions observed.

Types of changes

• Bug fix
• New feature
• Breaking change
• Asset change
• Documentation change
• Plugin change (now Module change, but checkbox retained per template)

Checklist

• I have read the CONTRIBUTING document.
• My change requires a change to the core logic.
  • I have linked the project issue above.
• My change requires a change to the assets.
  • I have linked the asset issue above.
• My change requires a change to the documentation.
  • I have linked the documentation issue above.
• My change requires a change to a plugin.
  • I have linked the plugin issue above.