[TheWitness]

Description

Promotes the accumulated develop changelog to the syslog v5.0 release and bumps the plugin version.

• Renamed the --- develop --- changelog heading to --- 5.0 ---.
• Reordered the 5.0 entries into the standard grouping: security, then issue, then feature.
• Applied the agreed entry-type normalization:
  • Dropped dev:, refactor:, test: and ci: entries.
  • Folded change: and style: entries into feature:.
  • Converted bug: entries to issue:.
• Sorted numbered issue#NNN entries ascending at the top of the issue group, then plain issue: and feature: entries alphabetically by description.
• Updated INFO to version = 5.0. plugin_syslog_version() derives the version from INFO, so no setup.php change is required.

Related Issue

Release/versioning change for the 5.0 cut; aggregates the issues and features already landed on develop.

Motivation and Context

Cuts the next release of the Syslog plugin by finalizing the changelog and version metadata so the plugin reports v5.0.

How Has This Been Tested?

Documentation/metadata-only change (CHANGELOG.md and INFO). Verified:

• The reordered 5.0 section contains no leftover dev:, refactor:, test:, ci:, bug:, change:, or style: prefixes.
• Entry counts after normalization: 7 security, 16 numbered issue#NNN, 44 plain issue, 47 feature.
• INFO now reports version = 5.0, which plugin_syslog_version() reads directly.

Screenshots (if appropriate):

N/A

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Release / changelog and version metadata update

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation repository accordingly.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

🔵 Needs a closer look

The version bump activates schema and hash migrations, but metadata/source tests do not verify that an installed 4.11-to-5.0 upgrade preserves data, permissions, and stored-version persistence, requiring human validation before release.

No open issues 🎉

What changed in this PR

Finalizes the Cacti Syslog plugin’s v5.0 release by publishing the accumulated development notes and updating the plugin’s version metadata.

Changes:

• Promotes the changelog’s develop section to 5.0.
• Groups release notes into security, issue, and feature entries, normalizes prefixes, and removes development-only categories.
• Bumps INFO from 4.11 to 5.0, which plugin_syslog_version() reads directly.

File	Description
INFO	Sets the plugin version to 5.0.
CHANGELOG.md	Finalizes and organizes the v5.0 release notes.

_{Review effort: Balanced}