[Framework][Key rotation] Add OriginatingAddress followup reconciliation function for key rotations without a proof challenge

[alnoki]

Per discussion with @davidiw cc @gedigi @hariria @xbtmatt, addressed in #14309 and documented in aptos-foundation/AIPs#487

Currently, rotate_authentication_key_call does not update the OriginatingAddress table after a successful key rotation without a RotationProofChallenge.

• Add a public entry reconciliation function, for example of the form account::ensure_originating_address_for_account, which can be called after a successful key rotation via rotate_authentication_key_call.
• Optionally consider making the function private, via VM-level check that automatically calls the function for every transaction from an account.