Remove win32 for release pipelines - will trigger manually

[sxa]

Due to capacity issues on windows 64-bit systems which are used for testing both 32 and 64-bit Windows JDK builds and running five releases in parallel it makes sense to prioritise the 64-bit ones on the available hardware for all releases before the 32-bit ones. The simplest way to achieve this is to remove the 32-bit ones from the pipelines and trigger those manually - likely a day the 64-bit ones have run.

This PR therefore removes the x32Windows configurations from the three release pipelines where we build it (8, 11, 17)

I'm not putting this into master at the moment sine we should re-evaluate capacity post release when we enable additional ibmcloud windows machines as part of adoptium/infrastructure#3238 (comment)

[github-actions]

Thank you for creating a pull request!

Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work).

Code Quality and Contributing Guidelines

If you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before.

Tests

Github actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our testing documentation.

In order to run the advanced pipeline tests (executing a set of mock pipelines), it requires an admin to post run tests on this PR.
If you are not an admin, please ask for one's attention in #infrastructure on Slack or ping one here.
To run full set of tests, use "run tests"; a subset of tests on specific jdk version, use "run tests quick 11,21"

[steelhead31]

LGTM