fix: `isAuthorizedRaw` system contract method should support account num aliases (aka long zero)

Currently forbids accoun num aliases as per the _original_ version of HIP-632. But HIP-632 has been updated to remove that restriction.

* Remove check _against_ account num aliases
* Confirm it now works with account num aliases
* Confirm `isValidAlias` supports account num aliases (as is)
* Confirm `isAuthorized` supports account num aliases (as is).

No file or test is named. Start by locating the Java implementation and tests for isAuthorizedRaw, then compare its account-number alias check with the updated HIP-632 rule. Done means removing the restriction and confirming isAuthorizedRaw accepts account number aliases while isValidAlias and isAuthorized continue to support them.

Written by the indexing model from the issue text.