chore: clean up unused artifacts, add deprecated notices.

[HumairAK]

1. Remove crd viewer
2. Add deprecated warnings for v1 specific fields in dspa
3. Ignore linting on dspa_params.go, so ci does not fail when it sees statticheck deprecated errors
4. Update dspa_all_fields.yaml to reflect latest state of possible dspa configuration options

Testing instructions:

1. Deploy DSPO
2. Navigate to OCP API Explorer >DataSciencePipelinesApplication > create
3. enter deprecated fields, mouse over, make sure they list the notices, example:

[dsp-developers]

A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-610
An OCP cluster where you are logged in as cluster admin is required.

To use this image run the following:

cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines-operator.git
cd data-science-pipelines-operator/
git fetch origin pull/610/head
git checkout -b pullrequest 69fd88e012a02077bcb3a9e4d76ffc65dbe76d80
oc new-project opendatahub
make deploy IMG="quay.io/opendatahub/data-science-pipelines-operator:pr-610"

More instructions here on how to deploy and test a Data Science Pipelines Application.

[gregsheremeta]

hm, should we be bumping our API to v2alpha1 for DSP v2?

[gregsheremeta]

also, depending on the answer to the above, we may want to say "v1alpha1" here. I think you mean "DSP v1" when you say "v1", but in this CRD API file, "v1" means a kubernetes API and not a version of the project. It could cause confusion.

[HumairAK]

hm, should we be bumping our API to v2alpha1 for DSP v2?

This is something we should have probably considered way ahead of time. I think crd version conversion strategy is upto us to decide when we do it. I'm not sure what the standard practice is here, but I don't think we should update the version of the crd this close to release, it would be difficult to account for all edge cases we need to handle.

I updated v1 to say "DSP V1" however.

[dsp-developers]

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-610

[gregsheremeta]

/lgtm

[dsp-developers]

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-610

[DharmitD]

Changes lgtm, and since the CI checks also pass

/Approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DharmitD

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

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

[gregsheremeta]

/lgtm