Context: During point-in-time backup/restore we may take a checkpoint at a specific timestamp Tbackup, and then replay all the oplog entries in the range from Tbackup to Trestore.

The backup may be selective i.e. only some collections may be backed up, while others are skipped.

However during PIT restore, all oplog entries are replayed, and it is expected that if they belong to a skipped collection, then it will become a no-op, e.g.:

• For a CRUD operation it may throw NamespaceNotFound and be ignored.
• For renameCollectionForApplyOps we throw a NamespaceNotFound which is then ignored by the oplog applier.

Issue: If we are replaying an upgradeDowngradeViewlessTimeseries oplog command entry for a skipped collection, we correctly detect that it can not be applied. However we then incorrectly conclude that this is unexpected and tassert.

We should instead handle it like in the rename case above.