Notify about dynamic plugin's file name constraints.

[gazarenkov]

Description

The problem is that dynamic plugins are silently not loaded in a case if the configured filename (key) in the configMap is not "dynamic-plugins.yaml" (as required by dynamic-plugins initContainer)
This PR makes deployment fail with error message in log.
For further improvement it:

• will be added to configuration doc ( Configuration documentation #129 )
• (optionally) to add somewhere to status

Which issue(s) does this PR fix or relate to

https://issues.redhat.com/browse/RHIDP-1740

PR acceptance criteria

• Tests

[sonarcloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.5% Duplication on New Code

See analysis details on SonarCloud

[gazarenkov]

Previous cherry-pick comment edited by @rm3l to prevent the automated cherry-pick PR from being created.

This will need to be cherry-picked later into the next patch release planned (1.2.1).
So we will cherry-pick this later into the 1.2.x branch right after the 1.2.0 release of RHDH is out.

[openshift-cherrypick-robot]

@gazarenkov: once the present PR merges, I will cherry-pick it on top of 1.2.x in a new PR and assign it to you.

In response to this:

/cherry-pick 1.2.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[github-actions]

PR images are available:

1. https://quay.io/janus-idp/operator:0.3.0-pr-381-760781b
2. https://quay.io/janus-idp/operator-bundle:0.3.0-pr-381-760781b
3. https://quay.io/janus-idp/operator-catalog:0.3.0-pr-381-760781b

[rm3l]

But this will need to be cherry-picked later into the next patch release planned (1.2.1).
So we will cherry-pick this later into the 1.2.x branch right after the 1.2.0 release of RHDH is out.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rm3l

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rm3l]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment