Remove observability from alpha1

[tataruty]

Proposed changes

Problem:
We need to remove v1alpha1 version of the Observability API in the future. We are supporting a newer version v1alpha2 for Observability API now.
#2986 to support the newer version.

Solution: Remove observability from v1alpha1.

Testing: Functional and unit tests
tested upgrade:

Closes #2767

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Release notes

If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

Remove deprecated v1alpha1 Observability API

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.09%. Comparing base (96032ac) to head (76b32ef).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4215   +/-   ##
=======================================
  Coverage   86.09%   86.09%           
=======================================
  Files         131      131           
  Lines       14171    14171           
  Branches       35       35           
=======================================
  Hits        12200    12200           
  Misses       1767     1767           
  Partials      204      204           

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ciarams87]

@tataruty We should add a release note too that we removed this deprecated API

[salonichf5]

Can we update the description on what happens when we use that API version? Could you check the upgrade process? For example if a user is using this version and we delete it -- what does the user see? or does it get automatically upgraded?

Looks good to me otherwise

[tataruty]

Can we update the description on what happens when we use that API version? Could you check the upgrade process? For example if a user is using this version and we delete it -- what does the user see? or does it get automatically upgraded?

Looks good to me otherwise

@salonichf5 it seems automatically upgraded without any error, you can see screenshot attached to the description

[salonichf5]

great job