HDDS-10916. Reduce Recon OM snapshot task initial delay in acceptance tests

[arunsarin85]

…ker-config

What changes were proposed in this pull request?

This patch sets ozone.recon.om.snapshot.task.initial.delay=20s in the docker-config files used by the Ozone Docker Compose stacks (e.g. ozone, ozone-topology, restart, and upgrade ha / non-ha), next to the existing ozone.recon.om.snapshot.task.interval.delay=1m, so Recon waits longer before the first OM snapshot in those environments - consistent with the secure compose stacks and intended to stabilize Recon namespace summary behavior in acceptance tests.

What is the link to the Apache JIRA

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

How was this patch tested?

• mvn -pl hadoop-ozone/dist package -am -DskipTests (or compile -am) so compose is staged under dist/target/ozone-*-SNAPSHOT/compose/.
• compose/ozone: execute_robot_test scm recon/recon-nssummary.robot - 16 passed.

• compose/ozone-topology: confirmed ozone.recon.om.snapshot.task.initial.delay is 20s in Recon’s ozone-site.xml; recon-nssummary.robot - 16 passed.

• compose/restart: confirmed initial.delay=20s and interval.delay=1m in Recon’s ozone-site.xml.
• compose/upgrade: verified OZONE-SITE.XML_ozone.recon.om.snapshot.task.initial.delay=20s in packaged ha and non-ha docker-config files.

[adoroszlai]

Thanks @arunsarin85 for the patch.