[BUG] When using create LRONConfig api for the first time, concurrent invocation returns resource_already_exists_exception

[zhichao-aws]

What is the bug?
When using create LRONConfig api of index operation notification for the first time at multi-node clusters, concurrent invocation leads to resource_already_exists_exception.
The first time of using Notification settings page will also return this exception.
Call the api one more time will create the LRONConfig successfully.

What is the expected behavior?
Concurrent invocation shouldn't return resource_already_exists_exception.

What is your host/environment?

• 2 node opensearch clusters

Do you have any screenshots?
If applicable, add screenshots to help explain your problem.

Do you have any additional context?
Add any other context about the problem.