Add deprecated stacks filtering to registry-library

[thepetk]

Please specify the area for this PR

/area registry-library

What does does this PR do / why we need it:

After the implementation for https://github.com/api/issues/959 we have now the ability of filtering the registry index for deprecated or non deprecated stacks by adding a deprecated=true/false parameter in the URL.

This PR updates the registry-library importing the same logic followed to the index server too.

Which issue(s) this PR fixes:

Fixes devfile/api#1065

PR acceptance criteria:

• Test Coverage
  • Are your changes sufficiently tested, and are any applicable test cases added or updated to cover your changes?

Documentation (WIP)

• Does the REST API doc need to be updated with your changes?
• Does the registry library doc need to be updated with your changes?

How to test changes / Special notes to the reviewer:

[openshift-ci]

@thepetk: The label(s) area/registry-library cannot be applied, because the repository doesn't have them.

In response to this:

Please specify the area for this PR

/area registry-library

What does does this PR do / why we need it:

After the implementation for https://github.com/api/issues/959 we have now the ability of filtering the registry index for deprecated or non deprecated stacks by adding a deprecated=true/false parameter in the URL.

This PR updates the registry-library importing the same logic followed to the index server too.

Which issue(s) this PR fixes:

Fixes devfile/api#1065

PR acceptance criteria:

• Test Coverage
  • Are your changes sufficiently tested, and are any applicable test cases added or updated to cover your changes?

Documentation (WIP)

• Does the REST API doc need to be updated with your changes?
• Does the registry library doc need to be updated with your changes?

How to test changes / Special notes to the reviewer:

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/test-infra repository.

[michael-valdron]

I would reflect these changes in other areas as well (docs and testing):

[michael-valdron]

/lgtm

[michael-valdron]

Change the value of index/server/tests/registry/stacks/java-springboot/devfile.yaml#L9 to our sprintboot logo to get around this https://raw.githubusercontent.com/devfile-samples/devfile-stack-icons/main/spring.svg

[thepetk]

Change the value of index/server/tests/registry/stacks/java-springboot/devfile.yaml#L9 to our sprintboot logo to get around this https://raw.githubusercontent.com/devfile-samples/devfile-stack-icons/main/spring.svg

I've added this change to all places where the icon was mentioned. Although I think better if we open an issue for a more permanent solution around this. I think a good approach here could be to try to gather all test resources into a single directory, shared between the modules of the repo. WDYT?

[michael-valdron]

Change the value of index/server/tests/registry/stacks/java-springboot/devfile.yaml#L9 to our sprintboot logo to get around this https://raw.githubusercontent.com/devfile-samples/devfile-stack-icons/main/spring.svg

I've added this change to all places where the icon was mentioned. Although I think better if we open an issue for a more permanent solution around this. I think a good approach here could be to try to gather all test resources into a single directory, shared between the modules of the repo. WDYT?

@thepetk I agree, an issue should opened to do this instead, I'd suggest everything should use registry-support/tests/registry instead so the content from all the individual ones should be migrated there and unit test source should point there.

[michael-valdron]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: michael-valdron, thepetk

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 [michael-valdron,thepetk]

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