For recoverFromOplogAsStandalone, we have this to set up the oplog collection pointer correctly before running any replication recovery. And this is needed since SERVER-45626 to use the AutoGetOplog helper.

But we are missing the acquireOplogCollectionForLogging call in recoverFromOplogUpTo. Additionally, the oplog name in LocalOplogInfo is not set up correctly read-only mode with recoverToOplogTimestamp (it only considers the recoverFromOplogAsStandalone case).

Last but not least, we dont seem to have any integration test coverages for running the server in readOnly mode with the recoverToOplogTimestamp server parameter.