HDDS-9943. TokenRenewer should close OzoneClient after use

[adoroszlai]

What changes were proposed in this pull request?

Ozone's TokenRenewer implementations do not close OzoneClient after use.

Both O3FS and OFS define their own TokenRenewer implementation.

Hadoop finds implementations via ServiceLoader, and uses the first one that handles the kind of token being used:

https://github.com/apache/hadoop/blob/7db9895000860605a66dd6403005b0c61a6ed744/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/token/Token.java#L454-L470

The two implementations are the same (not FileSystem-specific), kind is the same for both, so we can remove the duplicate one.

https://issues.apache.org/jira/browse/HDDS-9943

How was this patch tested?

Ran ozonesecure-mr/test.sh, checked OM audit log for delegation token operations:

...  | OMAudit | user=hadoop/[email protected] | ip=172.31.0.11 | op=GET_DELEGATION_TOKEN {kind=OzoneToken, service=172.31.0.9:9862, renewer=rm} | ret=SUCCESS |  
...  | OMAudit | user=rm/[email protected] | ip=172.31.0.11 | op=RENEW_DELEGATION_TOKEN {kind=OzoneToken, service=172.31.0.9:9862, renewer=rm} | ret=SUCCESS |  
...  | OMAudit | user=hadoop/[email protected] | ip=172.31.0.11 | op=GET_DELEGATION_TOKEN {kind=OzoneToken, service=172.31.0.9:9862, renewer=rm} | ret=SUCCESS |  
...  | OMAudit | user=rm/[email protected] | ip=172.31.0.11 | op=RENEW_DELEGATION_TOKEN {kind=OzoneToken, service=172.31.0.9:9862, renewer=rm} | ret=SUCCESS |  
...  | OMAudit | user=rm/[email protected] | ip=172.31.0.11 | op=CANCEL_DELEGATION_TOKEN {kind=OzoneToken, service=172.31.0.9:9862} | ret=SUCCESS |  
...  | OMAudit | user=rm/[email protected] | ip=172.31.0.11 | op=CANCEL_DELEGATION_TOKEN {kind=OzoneToken, service=172.31.0.9:9862} | ret=SUCCESS |  

CI:
https://github.com/adoroszlai/ozone/actions/runs/7237484751

[jojochuang]

Good catch, thanks!

[adoroszlai]

Thanks @jojochuang for the review.