[token-client] Make close_context_state_account and close_record_account variable order consistent

[samkim-crypto]

Problem

There is an inconsistency in the parameter orders between the confidential_transfer_close_context_state and confidential_transfer_close_record_account functions.

• In confidential_transfer_close_context_state, the lamport destination account is before the context state authority
• In confidential_transfer_close_record_account, the lamport destination comes after the context state authority

Summary of Changes

I updated confidential_transfer_close_record_account function to follow the confidential_transfer_close_context_state function. I also updated the confidential_transfer_close_context_state function name to confidential_transfer_close_context_state_account to be more consistent with the other functions.

Pull request has been modified.