Update Tracing Span's op names

[st0012]

Closes#1903

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 94.11765% with 2 lines in your changes missing coverage. Please review.

Project coverage is 98.43%. Comparing base (279df83) to head (a96e61b).
Report is 464 commits behind head on master.

Files with missing lines	Patch %	Lines
...ry/rails/tracing/active_storage_subscriber_spec.rb	50.00%	2 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## master #1923 +/- ##
=======================================
Coverage 98.43% 98.43% =======================================
Files 151 151 Lines 9283 9291 +8 =======================================
+ Hits 9138 9146 +8 
Misses 145 145 

☔ 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.

[st0012]

@sl0thentr0py I find it hard to categorize the change 🤔
Ideally matching the convention should give the users better span grouping...etc. on the Sentry side? I believe that's the goal but I'm not sure if that's been implemented. So this may be fit for enhancement?
But on the other hand, if users use span for filtering, this may break that. So it may be a breaking change too.

[sl0thentr0py]

@st0012@AbhiPrasad I think we decided to bite the bullet and just make it very clear in the changelogs that some dashboards might break and to migrate them over. We also collected some data and it didn't seem like there were a lot of users affected in general.

So we won't categorize this as a 'breaking' change in traditional terms but just add a clear changelog. Does that sound fine?

[dentarg]

Breaking change? Made us reach the transaction limit 💸

[Linuus]

Same here...