Updating v2 manifests to utilize DSPO namePrefix

[DharmitD]

The issue resolved by this Pull Request:

Resolves #378

Description of your changes:

Updated names of v2 manifests to remove mentions of Kfp, and utlize the data-science-pipelines-operator- namePrefix.
Updated serviceAccountname to serviceAccountName based on an error prompting to do so, while deploying v2.

Testing instructions

deployed a v2 instance using make v2deploy to make sure all resources came up with the data-science-pipelines-operator- prefix correctly.

Checklist

• The commits are squashed in a cohesive manner and have meaningful messages.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

[dsp-developers]

A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-405
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/405/head
git checkout -b pullrequest 1e26fd0c29a73025b39ae361742dd42d59c6fce6
make deploy IMG="quay.io/opendatahub/data-science-pipelines-operator:pr-405"

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

[rimolive]

/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-405

[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-405

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gmfrasca

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

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