Update devfile with ephemeral graphroot directory

[dkwon17]

What does this PR do?

Mounts an ephemeral volume to the graphroot directory. Without this change, out of space errors would occur for image builds.

This PR also updates the devfile tasks for building and pushing DWO images.

What issues does this PR fix or reference?

Is it tested? How?

To test, run the build-and-push-controller and make-olm-bundle-index-catalogsource devfile tasks. They should both run successfully.

PR Checklist

• E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)
  • v8-devworkspace-operator-e2e: DevWorkspace e2e test
  • v8-che-happy-path: Happy path for verification integration with Che

[dkwon17]

I've also added a view_catalogsource target:

$ make view_catalogsource 
To apply the CatalogSource, run:

oc apply -f - <<EOF
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: devworkspace-operator-catalog
  namespace: openshift-marketplace
spec:
  sourceType: grpc
  image: quay.io/devfile/devworkspace-operator-index:next
  publisher: Red Hat
  displayName: DevWorkspace Operator Catalog
  updateStrategy:
    registryPoll:
      interval: 5m
EOF

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 36.01%. Comparing base (129ce90) to head (dc825f8).
⚠️ Report is 29 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1576      +/-   ##
==========================================
+ Coverage   34.60%   36.01%   +1.41%     
==========================================
  Files         160      166       +6     
  Lines       13387    14283     +896     
==========================================
+ Hits         4632     5144     +512     
- Misses       8442     8798     +356     
- Partials      313      341      +28     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[rohanKanojia]

This is fine if the target cluster is always amd64, but it can be surprising if someone later targets an arm64 cluster.

[dkwon17]

I think for now, it's okay to only target amd64 for development. OOTB, I'm not able to build arm64 images in the workspace:

[2/2] STEP 1/11: FROM --platform=linux/arm64 registry.access.redhat.com/ubi9-minimal:9.6-1749489516
[2/2] STEP 2/11: RUN microdnf -y update &&     microdnf clean all &&     rm -rf /var/cache/yum &&     echo "Installed Packages" &&     rpm -qa | sort -V &&     echo "End Of Installed Packages"
process failed to start with error: fork/exec /bin/sh: exec format error
process exited with error: exec: not started
subprocess exited with status 1
Error: building at STEP "RUN microdnf -y update &&     microdnf clean all &&     rm -rf /var/cache/yum &&     echo "Installed Packages" &&     rpm -qa | sort -V &&     echo "End Of Installed Packages"": exit status 1

Let's add arm64 build functionality in a seperate PR

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dkwon17, rohanKanojia

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [dkwon17]

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

[openshift-ci]

New changes are detected. LGTM label has been removed.

[dkwon17]

After review with @btjd, there was an issue with quay.io/devfile/devworkspace-devtools:latest (quay.io/devfile/devworkspace-devtools:sha-0607887), where podman was not available in our cloud development environment.

However, I just tried it again, and podman is available:

Not sure what happened? Perhaps it's a cluster issue, and not an issue with this PR