Implement DevfileRegistry CRD MemoryLimit field

[thepetk]

Please specify the area for this PR

/area registry-operator

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

This PR introduces the MemoryLimit resource field for the DevfileRegistrySpecContainer - part of the DevfileRegistrySpec.

For each one of the DevfileRegistrySpecContainer included inside the DevfileRegistrySpec (e.g. DevfileIndex, OciRegistry & RegistryViewer) creates a getter function which assigns the default value in case the given value is nil or invalid.

New test cases have been added for the three getter functions.

Which issue(s) this PR fixes:

Fixes devfile/api#1428

PR acceptance criteria:

• Test Coverage
  • Are your changes sufficiently tested, and are any applicable test cases added or updated to cover your changes?
• Gosec scans
  • Fix all MEDIUM and higher findings and/or annotate a finding per gosec instructions: https://github.com/securego/gosec#annotating-code to address why a finding is not a security issue

Documentation

• Does the registry operator documentation need to be updated with your changes?

How to test changes / Special notes to the reviewer:

[openshift-ci]

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

In response to this:

Please specify the area for this PR

/area registry-operator

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

This PR introduces the MemoryLimit resource field for the DevfileRegistrySpecContainer - part of the DevfileRegistrySpec.

For each one of the DevfileRegistrySpecContainer included inside the DevfileRegistrySpec (e.g. DevfileIndex, OciRegistry & RegistryViewer) creates a getter function which assigns the default value in case the given value is nil or invalid.

New test cases have been added for the three getter functions.

Which issue(s) this PR fixes:

Fixes devfile/api#1428

PR acceptance criteria:

• Test Coverage
  • Are your changes sufficiently tested, and are any applicable test cases added or updated to cover your changes?
• Gosec scans
• Fix all MEDIUM and higher findings and/or annotate a finding per gosec instructions: https://github.com/securego/gosec#annotating-code to address why a finding is not a security issue

Documentation

• Does the registry operator documentation 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 27.10%. Comparing base (f55ab8e) to head (0642ab7).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #76      +/-   ##
==========================================
+ Coverage   25.30%   27.10%   +1.80%     
==========================================
  Files          25       25              
  Lines        1415     1428      +13     
==========================================
+ Hits          358      387      +29     
+ Misses       1032     1020      -12     
+ Partials       25       21       -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[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