An account to remove itself from being the autorenew account for any entity

### Problem

This came out from discussing from #ask-an-expert channel:
If an empty KeyList is sent as adminKey in ConsensuUpdateTopicTransactionBody, the adminKey is cleared. Without adminKey on a topic, only change allowed via an updateTopic is to extend the expirationTime. If there was an autoReviewAccount on the topic before clearing adminKey(because if no adminKey on a topic, there may not be an autoRenewAccount on the topic), should we also need to clear autoRenewAccount when an empty KeyList is sent as adminKey? This must have been done to prevent an account from getting trapped into forever being the auto-renew account for an immutable topic. Does this really make sense? Because unless the auto-renew account owner also controls the adminKey, it is already "trapped". And if the owner does control the topic adminKey, they are intentionally trapping themselves by making the topic immutable.

Leemon Barid answered:
I don’t think it should erase the autorenew account. It’s more logical to leave it.
But it should be possible for an account to remove itself from being the autorenew account for any entity. I don’t think that’s implemented yet. But that should be an issue to add it.

### Solution

Need to implement it.

### Alternatives

_No response_

Start by tracing the account and auto-renew behavior described around ConsensuUpdateTopicTransactionBody, including how an account is assigned as an autorenew account. The issue does not name files or tests, and the expected self-removal operation and completion criteria need to be clarified before implementation.

Written by the indexing model from the issue text.