feat: create hip-1021

[kantorcodes]

Description

This pull request introduces HIP-1021, titled "Improve Assignment of Auto-Renew Account ID for Topics." The proposal aims to enhance the Hedera Consensus Service (HCS) by automating the assignment of the autoRenewAccountId to the account that creates a TopicCreateTransaction. This feature is particularly useful when an Admin Key is not present during topic creation, ensuring that the auto-renewal mechanism is consistently applied.

The key changes include:

• Automatic Assignment: The autoRenewAccountId will automatically be set to the payer_account_id of the transaction if an Admin Key is not provided during topic creation.
• Retroactive Application: For existing topics that have only a Submit Key and no autoRenewAccountId, the original payer_account_id will be retroactively set as the autoRenewAccountId.
• Consistency and Error Reduction: This change aims to prevent user errors and ensure consistent management of topic renewals.

Improvements

1. Automatic Setting of Renewal Account:

   • The account that creates a topic will now automatically be used for renewals. Users don't need to manually set this anymore, making the process simpler and reducing the chance of mistakes.

2. Uniform Handling of Old Topics:

   • For older topics without a set renewal account, the system will automatically use the original account that created them for rent. This makes renewals consistent across all topics.

3. Fewer Mistakes:

   • By automating the setup of the renewal account, there’s a lower risk of topics accidentally expiring due to missing settings.

4. Easier for Users:

   • Users no longer need to worry about setting up renewal accounts; the system handles it automatically, making the overall process more user-friendly.

5. Ready for Future Changes:

   • This change also prepares the system for potential future updates, like introducing rent for topics, ensuring everything is correctly configured in advance.

[netlify]

✅ Deploy Preview for hedera-hips ready!

Name	Link
🔨 Latest commit	b1220b4
🔍 Latest deploy log	https://app.netlify.com/sites/hedera-hips/deploys/66ab78ba2541840008f1b5cd
😎 Deploy Preview	https://deploy-preview-1021--hedera-hips.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netopyr]

We should not modify existing topics IMO:

• We usually do not modify existing entities. A user may have left autoRenewAccount empty intentionally and disagrees with this change.
• This would have to be initiated outside of the consensus node because the consensus node does not store the original payer_account_id.
• It is unclear who should pay for these transactions.

[netopyr]

How would I be able to leave this field empty intentionally?
Another solution could be to set this as a default in the SDKs. This would give me a similar experience, but I would still be able to clear the autoRenewAccountId.