HDDS-8219. Run HA secure tests from s3g container

[adoroszlai]

What changes were proposed in this pull request?

In ozonesecure-ha environment SCM containers have hostnames like scm1.org, but all Kerberos principals for SCM nodes are in the form <username>/[email protected]. Since no host named scm exists, lookup takes quite some time:

$ OZONE_LOGLEVEL=TRACE ozone sh volume create /vol1 |& grep 'lookup'
[main] TRACE security.SecurityUtil: Name lookup for om2 took 1 ms.
[main] TRACE security.SecurityUtil: Name lookup for om3 took 0 ms.
[main] TRACE security.SecurityUtil: Name lookup for om1 took 0 ms.
[main] TRACE security.SecurityUtil: Name lookup for scm took 497 ms.

We can improve this simply by executing the same commands from another container, e.g. s3g:

$ OZONE_LOGLEVEL=TRACE ozone sh volume create /vol2 |& grep 'lookup'
[main] TRACE security.SecurityUtil: Name lookup for om2 took 1 ms.
[main] TRACE security.SecurityUtil: Name lookup for om3 took 0 ms.
[main] TRACE security.SecurityUtil: Name lookup for om1 took 0 ms.
[main] TRACE security.SecurityUtil: Name lookup for s3g took 0 ms.

Tests for bucket links need a minor change to remove hard-coded scm from permissions in test setup.

Opening as draft, since this is based on HDDS-7975 (#4437).

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

How was this patch tested?

Regular CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/4488033748

[smengcl]

Nice improvement. Thanks @adoroszlai .

[adoroszlai]

Thanks @kerneltime, @smengcl for the review.