Provide idempotent way to initialize history archive #5167
Description
Description
Explain in detail the additional functionality you would like to see in stellar-core.
I'd like to have a clean way to initialize history archive in an idempotent way.
Currently the new-hist command fails if the archive is already initialized
Explain why this feature is important
Similarly to #5166 such functionality will make it easier to run core in more dynamic environments, such as k8s.
Describe the solution you'd like
A new flag, such as --idempotent would be useful. This would allow operators to safely execute new-hist before core starts to make sure archive is initialized.
Describe alternatives you've considered
History can also be initialized by an operator manually but I'd like to remove manual steps.
It's also possible for operators to write wrappers or ignore exit code of the command. Both of those solution should work but they are not very clean and require extra work.