HIP-583 Always populate EVM address on accounts REST API

[steven-sheehy]

Problem

As an EVM user, I'd like to know the account's EVM address and search by it regardless of which type mentioned in HIP-583 it is.

Solution

• In the response of /api/v1/accounts and /api/v1/accounts/{id}, if the alias field is a 40 character (20 bytes) EVM address and evm_address field is null, populate evm_address with the alias
• In the response of /api/v1/accounts and /api/v1/accounts/{id}, populate the evm_address field with the account num alias (i.e. long zero entity id) form if it's null and not the scenario from above
• In all /api/v1/accounts/{id}/* APIs, if the ID in the request is an EVM address with all zero prefix to indicate it's an account num alias then convert to an entity ID and lookup using that

Alternatives

No response

[jascks]

@steven-sheehy, I'm less familiar with Node/Express etc., but is hedera-mirror-rest/account.js where I want to add this new logic?