Fetch status of all scenarios in DM in a single operation instead of separately for each scenario.

[mgoworko]

Describe your changes

Problem to be solved:

When fetching list of scenarios or status of all scenarios, for periodic scenarios there were always 2N db queries for N periodic scenarios. Those 2N queries were performed each time and endpoint /processes or /processes/status was called.

Solution:

1. Defined capability of DeploymentManager (StateQueryForAllScenariosSupported). This capability means, that the DM can fetch all scenarios in a single operation.

2. The new capability is implemented for PeriodicDeploymentManager and for FlinkStreamingDeploymentManagerProvider (which is an underlying DM of PeriodicDeploymentManager)

3. When fetching processes or status, Nu uses the more efficient implementation of StateQueryForAllScenariosSupported when it is present (and it is present for periodics).

4. This improvement can be implemented for other DM's too, but it is outside of the scope of this task. Moreover, we only have performance issues for periodic DM ATM.

Checklist before merge

• Related issue ID is placed at the beginning of PR title in [brackets] (can be GH issue or Nu Jira issue)
• Code is cleaned from temporary changes and commented out lines
• Parts of the code that are not easy to understand are documented in the code
• Changes are covered by automated tests
• Showcase in dev-application.conf added to demonstrate the feature
• Documentation added or updated
• Added entry in Changelog.md describing the change from the perspective of a public distribution user
• Added MigrationGuide.md entry in the appropriate subcategory if introducing a breaking change
• Verify that PR will be squashed during merge

[github-actions]

created: #7358
⚠️ Be careful! Snapshot changes are not necessarily the cause of the error. Check the logs.

[arkadius]

LGTM