chore: prepare release 2.0.0

[github-actions]

This PR was created automatically. Merging it will finalize the changelog for 2.0.0

2.0.0 (2024-12-20)

Breaking Changes

• Enforced S3 bucket name validation rules (#1722).
• Moved migrations to the autopilot (#1735).
• Removed contract sets (#1657).
• Removed support for multiple autopilots (#1657).
• Removed event webhooks (#1699).
• Removed partial setting updates (#1688).
• Updated ContractMetadata to exclude the host IP and siamux address (#1712).

Features

• Integrated RHP4 support (#1723, #1710, #1711, #1680, #1693).
• Added OpenAPI documentation and validation to the API (#1724, #1733, #1737).
• Monitors file contracts and unlocks funds upon expiration (#1720).
• Removed the "current period" concept from the contractor (#1692).
• Updated autopilot configuration by removing the ability to toggle redundant host IPs (#1692).
• Updated gouging settings to remove the migration surcharge multiplier (#1696).
• Updated UI to version v0.72.0. (#1764).

Fixes

• Automated changelog generation (#1681).
• Automatically reset account drift using rate limiting (#1714).
• Fixed a bug where the low max duration was not considered when fetching hosts (#1755).
• Fixed default settings not being applied if missing in the database (#1761).
• Fixed a bug in host sector deletion (#1762).
• Fixed various non-deterministic failures (NDFs) in tests.
• Added contract_elements table to track accumulator state elements for file contracts (#1703).
• Added host_sectors table to track which sectors are stored on which hosts (#1704).

[peterjan]

@n8maninger I cleaned up the changelog, what I'm not sure is how to effectively tag the alpha and when. Are we going to tag v2.0.0-alpha.1 and should that be reflected in the changelog?