ci(json-schema-check): allow nested config paths

[amadeuszsz]

Description

Currently, json-schema-check considers only specific files match: schema/<schema_cfg_name>.schema.json and config/<schema_cfg_name>.param.yaml. For packages with many config files, the config directory structure may differ. Even though the files follow naming convention, the sub directories are not taken into account. This small change in pull request adds following naming convention: schema/<schema_cfg_name>.schema.json and config/<namespace>/<schema_cfg_name>.param.yaml.

Tests performed

Checked locally with CI script few test cases, success stands for Validating ... and fail stands for No configuration files found for schema ... or schema was not found.

1. Expected success.

<package_name>
      |
      |—— schema
      |     |—— <schema_cfg_name>.schema.json
      |
      |—— config
      |     |—— <schema_cfg_name>.param.yaml
      |

Current: ${\color{green}SUCCESS}$
Proposed: ${\color{green}SUCCESS}$

2. Expected success.

<package_name>
      |
      |—— schema
      |     |—— <schema_cfg_name>.schema.json
      |
      |—— config
      |     |—— <namespace>
      |              |
      |              |—— <schema_cfg_name>.param.yaml
      |

Current: ${\color{red}FAIL}$
Proposed: ${\color{green}SUCCESS}$

Effects on system behavior

Not applicable.

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

[drwnz]

LGTM