Expiration date is confusing until account expiry is turned in.

[svienot]

Description

From Christian Hasker:
This is confusing to folks. I know account expiry isn't turned on yet, so should we overwrite this with a 'not applicable' or 'auto-renew' or something?

From Giuseppe Bertone:
If I check this token on the mirror node, it actually has those values set:

  "auto_renew_account": "0.0.700000",
  "auto_renew_period": 7776000,
  "expiry_timestamp": 1692650180374734000,

The HashScan interface currently shows “not enabled yet” for “auto renew account” and “auto renew period”, that is “true”, but technically inaccurate because users asked for a different information (he asked for token details, and token details say those fields are set).
My suggestion is to show all the correct data, with a note/tooltip about what’s enabled and what’s not enabled yet, or to simply hide everything.

Steps to reproduce

https://hashscan.io/mainnet/account/0.0.2908012

Additional context

No response

Hedera network

mainnet, testnet, previewnet

Version

Release v23.5.0-3-geba9d82

Operating system

None