test: remove unused test-e2e Makefile target

[ekam-walia]

What type of PR is this:
/kind cleanup
/area testing

What this PR does / why we need it:

Removes the now-unused test-e2e Makefile target since test-e2e-baseline
and test-e2e-extended are the only targets used after the singlecluster
e2e split in #11138.

Which issue(s) this PR fixes:

Part of #10995

Special notes for your reviewer:

Follow-up cleanup after #11138 which split the singlecluster e2e tests
into baseline and extended.

Does this PR introduce a user-facing change:

NONE

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue ready!

Name	Link
🔨 Latest commit	8d9bf87
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-kueue/deploys/6a09d110c982010007467d12
😎 Deploy Preview	https://deploy-preview-11262--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[k8s-ci-robot]

Hi @ekam-walia. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kannon92]

/ok-to-test

[kaisoz]

nit: IMO I'd keep test-e2e instead of test-e2e-baseline. The former reads more natural to me and is easier to remember bc of historical reasons . Also test-e2e-extended combines perfectly

WDYT @kannon92 ?

[mimowo]

/lgtm
/approve
/cherrypick release-0.17
/cherrypick release-0.16
Thank you, this PR will help to keep the codebase clean

[k8s-infra-cherrypick-robot]

@mimowo: once the present PR merges, I will cherry-pick it on top of release-0.16, release-0.17 in new PRs and assign them to you.

Details

In response to this:

/lgtm
/approve
/cherrypick release-0.17
/cherrypick release-0.16
Thank you, this PR will help to keep the codebase clean

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ekam-walia, mimowo

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:

• OWNERS [mimowo]

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

[k8s-ci-robot]

LGTM label has been added.

Details

Git tree hash: 384f86e07ecb9239dff2a34681226b9abb731ceb

[k8s-infra-cherrypick-robot]

@mimowo: new pull request created: #11268

Details

In response to this:

/lgtm
/approve
/cherrypick release-0.17
/cherrypick release-0.16
Thank you, this PR will help to keep the codebase clean

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-infra-cherrypick-robot]

@mimowo: new pull request created: #11269

Details

In response to this:

/lgtm
/approve
/cherrypick release-0.17
/cherrypick release-0.16
Thank you, this PR will help to keep the codebase clean

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.