github: Remove check-vep workflow from release-1.8-aie-nv

[lyarwood]

What this PR does

It's failing as we don't have the same project secrets as kubevirt/kubevirt:

Run python automation/label-approved-veps.py
Traceback (most recent call last):
  File "/home/runner/work/kubevirt-aie/kubevirt-aie/automation/label-approved-veps.py", line 301, in <module>
    main()
    ~~~~^^
  File "/home/runner/work/kubevirt-aie/kubevirt-aie/automation/label-approved-veps.py", line 254, in main
    pr_body = get_pr_details()
  File "/home/runner/work/kubevirt-aie/kubevirt-aie/automation/label-approved-veps.py", line 61, in get_pr_details
    response.raise_for_status()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/opt/hostedtoolcache/Python/3.14.3/x64/lib/python3.14/site-packages/requests/models.py", line 1026, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://api.github.com/repos/kubevirt/kubevirt-aie/pulls/4
Error: Process completed with exit code 1.

The workflow doesn't make sense on this branch so remove it.

References

Why we need it and why it was done in this way

The following tradeoffs were made:

The following alternatives were considered:

Links to places where the discussion took place:

Special notes for your reviewer

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least one e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered
• AI Contributions: The PR abides by the KubeVirt AI Contribution Policy.

Release note

NONE

[fossedihelm]

/lgtm

[jean-edouard]

/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jean-edouard, lyarwood

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• .github/OWNERS [jean-edouard]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment