Prevent disabled vote sites from being auto-created

[BenCodez]

Motivation

Disabled vote sites are intentionally excluded from the in-memory list of loaded sites. That made a configured-but-disabled site look missing during vote ingestion, allowing AutoCreateVoteSites to generate the same site again with Enabled: true.

Implementation

• Added ConfigVoteSites#getRawVoteSiteNames() to return actual VoteSites configuration sections without filtering on Enabled or validating site settings.
• Added configured-site resolution in VoteSiteManager for:
  • exact keys;
  • normalized keys such as site.example → site_example;
  • non-empty ServiceSite values;
  • non-empty display names.
• Added hasConfiguredVoteSite(String...) while preserving hasVoteSite(...) as a loaded-site check.
• Blocked auto-creation in both:
  • VoteSiteManager#getVoteSite(...);
  • the explicit generation path in VotiferEvent.
• Added null handling without changing enabled-only lookup behavior.

Regression coverage

Added 14 focused tests covering:

• enabled and disabled raw configuration sections;
• malformed scalar entries and malformed/missing VoteSites roots;
• configured-site matching by key, normalized key, ServiceSite, and display name;
• multiple identifiers, null values, and empty aliases;
• loaded-versus-configured site semantics;
• prevention of disabled-site generation;
• preservation of auto-generation for genuinely unknown sites;
• both VoteSiteManager and Votifier ingestion paths.

Verification

• Final clean diff contains exactly three production files and three test files.
• GitHub Actions Java CI with Maven run Use new config api #403 passed on the final branch head.
• Full Maven package result: 271 tests, 0 failures, 0 errors, 0 skipped.

AI disclosure

This pull request was created with assistance from OpenAI and reviewed by BenCodez.