[CI] make Nightly-build CI run on changes to CI

[icfaust]

Description

With the merge of intel/scikit-learn-intelex#2147, runs of Nightly-build are only taken from scheduled or workflow dispatches. This allows for testing the nightly without disrupting sklearnex CI when changes to CI, make system, or the nightly are made in PRs. This will make it less blind, and verification by reviewers easier/less by faith. If changes are made to CI, then nightly-build will run on the PR. This will not be run on main push.

NOTE: This PR fixes two CI issues which have shown up:

1. A qemu install from deb package issue, which the version and dependencies have changed
2. An issue in building the nightly on windows with a VS/DPCPP hybrid build caused by changes introduced in fix(make): enabling debug build #2946

---

PR should start as a draft, then move to ready for review state after CI is passed and all applicable checkboxes are closed.
This approach ensures that reviewers don't spend extra time asking for regular requirements.

You can remove a checkbox as not applicable only if it doesn't relate to this PR in any way.
For example, PR with docs update doesn't require checkboxes for performance while PR with any change in actual code should have checkboxes and justify how this code change is expected to affect performance (or justification should be self-evident).

Checklist to comply with before moving PR from draft:

PR completeness and readability

• I have reviewed my changes thoroughly before submitting this pull request.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes or created a separate PR with update and provided its number in the description, if necessary.
• Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
• I have added a respective label(s) to PR if I have a permission for that.
• I have resolved any merge conflicts that might occur with the base branch.

Testing

• I have run it locally and tested the changes extensively.
• All CI jobs are green or I have provided justification why they aren't.
• I have extended testing suite if new functionality was introduced in this PR.

Performance

• I have measured performance for affected algorithms using scikit-learn_bench and provided at least summary table with measured data, if performance change is expected.
• I have provided justification why performance has changed or why changes are not expected.
• I have provided justification why quality metrics have changed or why changes are not expected.
• I have extended benchmarking suite and provided corresponding scikit-learn_bench PR if new measurable functionality was introduced in this PR.