New custom action behaviour

[vder]

Describe your changes

In current implementation of custom actions state of the actions depends only on scenario's status. The following change makes this mechanism little more flexible. Now buttons can be enabled/disabled according to the visible scenario version and last deployment action as well. In particular we want to enable custom action only in case when deployed version of the scenario is visible in designer.

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