feat: split custom severity events (#456), seed CUSTOM_CONFIG_KEY in …

[Tenny150]

…initialize (#455), re-document rent estimate (#459)

• set_custom_severity overwrites in place with no created/updated distinction: indexers cannot tell first registration from reconfiguration #456: Add sev_add/sev_upd/cfg_rem events to distinguish custom severity creation, reconfiguration, and removal — indexers can now reconstruct the registered set from events alone
• initialize does not seed CUSTOM_CONFIG_KEY while migrate's init_missing_storage_defaults does: fresh and migrated contracts have different storage layouts for the same logical state #455: Seed CUSTOM_CONFIG_KEY in initialize() so fresh and migrated contracts have the same instance-storage key layout
• get_rent_estimate returns a made-up formula (footprint/10+1): operators budget rent using numbers with no network-source attribution #459: Re-document get_rent_estimate as a relative growth proxy with explicit disclaimer (formula is not derived from network parameters)

Closes #455, #456, #459

🤖 Generated with Codebuff

Description

Brief description of the changes in this PR.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Related Issues

Fixes #(issue number) or relates to #(issue number)

Changes Made

Testing

Describe the testing performed to validate these changes:

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented complex logic
• I have updated relevant documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• My changes do not introduce new warnings

Screenshots (if applicable)

Add screenshots or logs if applicable.

closes #462
closes #459
closes #456
closes #455

[drips-wave]

@Tenny150 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[usmanimamu17-create]

Approved, good work.

[usmanimamu17-create]

LGTM, nice work 👍