PBM-1391: Enabling PITR after physical restore causes PSMDB to crash

[boris-ilijic]

PR for https://perconadev.atlassian.net/browse/PBM-1391

After physical restore with PITR, all PSMDB secondary nodes fail with the fatal error:

{"t":{"$date":"2024-09-12T06:12:55.515+00:00"},"s":"F",  "c":"ASSERT",   "id":23081,   "ctx":"ReplWriterWorker-6","msg":"Invariant failure","attr":{"expr":"!needsRenaming || allowRenameOutOfTheWay","msg":"Current collection name: (None), UUID: 0ea5a363-872c-4380-87c6-ff426f0b0a85. Future collection name: admin.pbmPITR","file":"src/mongo/db/catalog/create_collection.cpp","line":835}}
{"t":{"$date":"2024-09-12T06:12:55.515+00:00"},"s":"F",  "c":"ASSERT",   "id":23082,   "ctx":"ReplWriterWorker-6","msg":"\n\n***aborting after invariant() failure\n\n"}
{"t":{"$date":"2024-09-12T06:12:55.515+00:00"},"s":"F",  "c":"CONTROL",  "id":6384300, "ctx":"ReplWriterWorker-6","msg":"Writing fatal message","attr":{"message":"\n"}}
{"t":{"$date":"2024-09-12T06:12:55.515+00:00"},"s":"F",  "c":"CONTROL",  "id":6384300, "ctx":"ReplWriterWorker-6","msg":"Writing fatal message","attr":{"message":"Got signal: 6 (Aborted).\n"}}

due to the fact that Primary and Secondary have DDL operations executed in different order:

• Primary: PITR apply -> dropping PBM collections
• Secondary: dropping PBM collections -> applying PITR (during sync from Primary)

This PR fixes the problem by omitting DDL operation (primary drop) on PBM's collection during the physical restore phase and replacing it with delete all operation.
PR also creates all remaining PBM system collections at the first start of the PBM Agent to reduce the DDL operation within PITR.