ci(i): Make change detector an independent workflow

[shahzadlone]

Relevant issue(s)

Resolves #2736

Description

• Move change detection to a separate workflow to not block code coverage upload to be dependent / blocked by it.
• More reasons in the issue (split change detector action into a separate job, or a separate workflow completely #2736) on why we want this.

Note will need to change required checks naming, will do it pre-merge and after an approval.

How has this been tested?

• Manually

Specify the platform(s) on which this was tested:

• WSL2

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.90%. Comparing base (343ec38) to head (a630a3f).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #2789      +/-   ##
===========================================
+ Coverage    78.84%   78.90%   +0.06%     
===========================================
  Files          315      315              
  Lines        23835    23835              
===========================================
+ Hits         18792    18806      +14     
+ Misses        3669     3663       -6     
+ Partials      1374     1366       -8     

Flag	Coverage Δ
all-tests	78.90% <ø> (+0.06%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 11 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 343ec38...a630a3f. Read the comment docs.

[nasdf]

LGTM. This is a much better approach than including it in the test matrix.