deprecate-api validator: add checks for removed APIs on 1.25 and 1.26

[camilamacedo86]

Description
deprecate-api validator: add checks for removed APIs on 1.25 and 1.26

Motivation
If we found the removed APIs for 1.25 and 1.26 raise the warnings and errors accordingly.

Co-authored-by: Brett Tofel [email protected]

Closes: #151
Closes: #157

[bentito]

/lgtm

[bentito]

/lgtm

[gallettilance]

Looks good! Can you please add an example of how to call this validation in the README?

[camilamacedo86]

HI @gallettilance,

The README and the validator doc for the golang docs were supplemented. Thank you for your review. 🥇

[gallettilance]

/lgtm one nit: if they use these optional validators it would be good to produce a warning saying "deprecated apis were not detected. this validator cannot check operator code for the use of deprecated apis. please check your operator code to ensure that deprecated apis aren't in use." (something like that)

[camilamacedo86]

Hi @gallettilance:

/lgtm one nit: if they use these optional validators it would be good to produce a warning saying "deprecated apis were not detected. this validator cannot check operator code for the use of deprecated apis. please check your operator code to ensure that deprecated apps aren't in use." (something like that)

The validators just raise warnings or errors (no info level logs #158). If we always introduce a warn by default, how can we easily identify when the checks passed successfully (nothing to report, not found) when not? For example, I want my report shows the result in yellow when any warning is raised and in red when we found an issue.

I think that would be nice to be provided if we be able to do #158 and began to have an info level then, we could add this info by default.

[ankitathomas]

/lgtm

[dinhxuanvu]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, dinhxuanvu

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 [dinhxuanvu]

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