[Subtask]: In master-slave mode, each AMS should automatically senses the optimizer.

[wardlican]

Why are the changes needed?

In master-slave mode, each optimizer needs to communicate with each ams node. Therefore, the registration mode of the optimizer needs to be modified in master-slave mode. The optimizer only reports heartbeats to the master node. Only the master node will maintain whether the optimizer's heartbeat has timed out. The slave node loads optimizer information from the database to detect whether there are any new or deleted optimizers.

Close #3929 .

Brief change log

• In master-slave mode, only the master node is responsible for maintaining the addition and expiration of optimizers.
• Slave nodes periodically detect the addition and deletion of optimizers from the database.

How was this patch tested?

• Add some test cases that check the changes thoroughly including negative and positive cases if possible

• Add screenshots for manual tests if appropriate

• Run test locally before making a pull request

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)