BUG: TimeableNodeVisibilityService failing if not all content dimensions are initialized

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

1. Create multiple dimensions with at least one mapping having not been initialized correctly
2. Run ./flow timeablenodevisibility:execute
3. Throws

Expected Behavior

Does not throw and actually handles the visibility changes for the working dimensions correctly.

Steps To Reproduce

1. Create multiple dimensions with at least one mapping having not been initialized correctly
2. Run ./flow timeablenodevisibility:execute
3. Throws

Environment

- Flow: 9.1.0
- Neos: 9.1.3
- PHP: 8.3

Anything else?

Is this intended? In my opinion it could be beneficial to just log and continue so that the service works for the initialized dimensions.

Suggestion for reference: https://github.com/VolkerLieber/neos-development-collection/commit/5ff9751d2e76c45286dda7cb10dc7a689f0545f9