In SERVER-101952 we added a new timeseries/create_indexes.js FSM test, but we needed to tag it with `excluded_from_simuate_crash_suite` because on those suites the validate hook was failing with:

[hook:SimulateCrash:job2] | 2025-05-21T14:27:04.226+00:00 I  COMMAND  21962       [conn2] "Assertion while executing command","attr":{"command":"validate","db":"test7_fsmdb0","commandArgs":{"validate":"coll_1","lsid":{"id":{"$uuid":"3188ad33-9525-4d57-b7cb-5d166ae3d69f"}},"$db":"test7_fsmdb0"},"error":"NamespaceNotFound: Cannot validate a time-series collection without its bucket collection test7_fsmdb0.system.buckets.coll_1."}
[hook:SimulateCrash:job2] FAILURE!
Validate Response:
[hook:SimulateCrash:job2] {'ok': 0.0, 'errmsg': 'Cannot validate a time-series collection without its bucket collection test7_fsmdb0.system.buckets.coll_1.', 'code': 26, 'codeName': 'NamespaceNotFound'}

We should investigate further this issue. The main question is should it be possible to end-up with a view without its bucket collection? Considering that the creation of the view and the bucket collection are not replicated atomically and that this suites is simulating ndoe crashes I believe this is totally possible.

Considering that we are moving to viewless timeseries implementation we could also consider to re-enable this test only for viewless timeseries collection that shoudln't be suffering from the same problem since they don't have view+bucket duality.