Exclude files specifically changed for release from rc sync PR

[mehrdad2m]

Context:
During feature freeze, we need to modify some of the Github workflows on the release candidate branch. These changes should not be included in the daily sync that merged into main branch.

Description of the Change:

• Added the check-catalyst workflow which should be modified in feature freeze week to be excluded.
• Added files that are modified in the "Bump PennyLane and Lightning minimum versions" PR that is merged to rc on release day.

Benefits:
Less maintenance of the daily rc sync PR and therefore less risk for mistakenly merging unwanted code

Possible Drawbacks:
We would require a version bump PR on main after the release to bump the versions of Pennylane and Lightning.
Any change to the wheel builder scripts that actually need to be included in main should be applied separately but not sure if that is something that happens frequently.

Related GitHub Issues:

[mehrdad2m]

@dime10 , My original motivation was to only exclude the check-catalyst.yaml file, but not too sure about the rest. I am not sure how frequently we would have changes in the other files that want in the main too. Do you think it make sense to exclude them?

[github-actions]

Hello. You may have forgotten to update the changelog!
Please edit doc/releases/changelog-dev.md on your branch with:

• A one-to-two sentence description of the change. You may include a small working example for new features.
• A link back to this PR.
• Your name (or GitHub username) in the contributors section.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.87%. Comparing base (0d9585b) to head (6123f18).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1643   +/-   ##
=======================================
  Coverage   96.87%   96.87%           
=======================================
  Files          80       80           
  Lines        8831     8845   +14     
  Branches      837      839    +2     
=======================================
+ Hits         8555     8569   +14     
  Misses        222      222           
  Partials       54       54           

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

[paul0403]

Is this still relavant?

[dime10]

@dime10 , My original motivation was to only exclude the check-catalyst.yaml file, but not too sure about the rest. I am not sure how frequently we would have changes in the other files that want in the main too. Do you think it make sense to exclude them?

Thanks Mehrdad, yeah good question, this does look like a lot of files 🤔 I think all the actions are probably fine, since we do inject those patches there during the release process. The .dep-versions and doc/requirements.txt are also updated according to the release guide. For the Makefile and setup.py I'm not sure, we could leave those out for now and see later? The linux scripts are gone now (🎉), so that one can be removed :)