Harden feature cleanup after database startup failure

[remdui]

What changed

• Make Nametags cleanup safe when initialization fails before NametagManager exists.
• Replace generic empty-Optional NoSuchElementException failures with explicit ORM startup errors for ChatLog, CommandLogger, Glow, Nametags, and Sanctions.
• Preserve the framework's existing failure cleanup: failed features unregister listeners, commands, tasks, services, ORM contexts, and DataProvider scopes.

Root cause

The DataProvider access-policy failure stopped ORM-backed features during initialization. Nametags then dereferenced a null manager during partial cleanup, obscuring the primary failure and contributing to the secondary async Log4j rendering error.

Impact

• Partial initialization no longer creates a cleanup NPE.
• Database startup failures now identify the affected feature and required MYSQL/player_data_rw connection.
• The primary authorization fix remains Fix Paper shared connection access before plugin enable DataProvider#14; this PR makes ServerFeatures fail cleanly and diagnostically if database setup is unavailable for any other reason.