Collection verifying startup code in DeckPicker, IntentHandler (and others) also startup

The issue with #5072 has a root cause that is related to DeckPicker having all our startup code that is protective and makes sure we have access to the collection, but IntentHandler is also a valid startup pathway and doesn't always distribute control to DeckPicker.

The protective code from DeckPicker's startup area needs to move to a dedicated "startup" area and all entry points should reference it.

This could be contemplated at the same time as a full database migration solution #5120 since it would also need to run on startup every time