ApiVersion displayed on console is v1alpha1 whereas we support v1beta1

While creating a build via console, the YAML of build or buildRun switched to shipwright.io/v1alpha1 version, whereas we support shipwright.io/v1beta1 with GA.

Also, once the builds/buildRuns are created, the same buildRun will have v1alpha1 version yaml on console, and v1beta1 version yaml when checked through CLI.

Concerns:
- The mismatch of apiVersion on console vs CLI could be really confusing for customers.
- All our documents has v1beta1 references, and if a user is completely dependent on console, they might not be able to configure the builds easily.

OCP 4.14
builds for OpenShift v1.0.0

Always

1. Deploy the builds for Red Hat OpenShift release candidate operator
2. Go to the "Developer preview" and create a Build via console. Specify the following yaml definition:
~~~
apiVersion: shipwright.io/v1beta1
kind: Build
metadata:
  name: buildah-golang-build
spec:
  source:
    git:
      url: https://github.com/shipwright-io/sample-go
    contextDir: docker-build
  strategy:
    name: buildah
    kind: ClusterBuildStrategy
  paramValues:
  - name: dockerfile
    value: Dockerfile
  output:
    image: image-registry.openshift-image-registry.svc:5000/<namespace>/sample-go-app
~~~
3. Once the build is created, start the build.
4. Check the yamls of build & buildRun, vs, the yaml through CLI:
   $ oc get builds.shipwright.io buildah-golang-build -oyaml
   $ oc get br <buildah-golang-buildrun-name> -oyaml
5. Observe the difference in apiVersions being referred.

The apiVersions are different for the same object.

The apiVersions should be in sync (console & CLI).

This issue is not observed for OCP 4.15 nightly.