Timeout when changing timezone system parameter

[Douglas Gameiro Diniz]

Brief Description
-----------------
After the execution of the "system modify --timezone" command, a RPC timeout error is thrown on some occasions.

Severity
--------
Minor

Steps to Reproduce
------------------
There is a test case that can reproduce the problem. The test sets the timezone to a region, do a swact and then sets the timezone back to UTC. After the swact, the main controller will thrown a Timeout when changing the timezone to UTC. The problem only occurred in an Standard lab with 2 controllers e 2 workers, and it needs to be installed with Openstack.

Expected Behavior
------------------
The timezone should be changed without any timeout error.

Actual Behavior
----------------
There is and RPC Timeout, but seems that the timezone is still changed correctly.

Reproducibility
---------------
The problem is intermitent. Using the testcase it happens around 80% of the time. It only occurred in a Standard lab with Openstack installed.

System Configuration
--------------------
Standard 2+2 with Openstack.

Branch/Pull Time/Commit
-----------------------

Last Pass
---------
This error is occurring for some time and there is no information about the last pass.

Timestamp/Logs
--------------

Test Activity
-------------
Developer Testing

Workaround
----------

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/config/+/891081

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/config/+/891081
Committed: https://opendev.org/starlingx/config/commit/a25eed08d52a7e321708c5ed42c8ac714e65f889
Submitter: "Zuul (22348)"
Branch: master

commit a25eed08d52a7e321708c5ed42c8ac714e65f889
Author: Douglas Gameiro Diniz <email address hidden>
Date: Thu Aug 10 11:40:12 2023 -0300

    RPC timeout when changing the system timezone

    This fix increases the 'configure_system_timezone' command timeout from
    60s, which is the default, to 90s. This command configures the
    controllers and the workers separately, so the original RPC coming from
    the Api only returns after the configuration is completed in the
    controllers and after the command is sent to the workers, which can take
    more than 60s in some environments that have Openstack deployed,
    especially after a swact. With Openstack installed, the command
    execution time increases considerably, being one of the main
    contributors to this timeout.

    Test Plan:
    Pass: Manually changed the code in a Standard lab with Openstack
    deployed, setting the timezone after a swact.
    Pass: Tested in a Standard VM installation, simulating the timeout with
    a sleep and checking that the change fixes the 60s threshold problem,
    running the tests locally.

    Closes-Bug: 2028280

    Change-Id: I6d2de89b0c0ab83da02206fb1ca2b6c69d846c7b
    Signed-off-by: Douglas Gameiro Diniz <email address hidden>