wheel-builder workflow should check both `pip install` and `uv pip install`

[ngoldbaum]

Right now the sanity checks for the wheels only use uv. Here's the Windows version but the other versions look similar:

cryptography/.github/workflows/wheel-builder.yml

Lines 401 to 406 in c52dea5

	- run: uv pip install cryptography --no-index -f wheelhouse/
	- name: Print the OpenSSL we built and linked against
	run: |
	echo "from cryptography.hazmat.backends.openssl.backend import backend;print('Loaded: ' + backend.openssl_version_text());print('Linked Against: ' + backend._ffi.string(backend._lib.OPENSSL_VERSION_TEXT).decode('ascii'))" | uv run -
	- uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2

I think it makes sense to check regular pip install too - I think that would have caught the issue fixed by #13448

[alex]

Recommended path forward here:

• First, let's take the steps for doing the smoketest against the wheel and put them into a re-usable action. These are currently duplicated between the different OSs. (Should be easy)
• Then let's add a flag to it to enable testing against pip. We can set this on a subset of our linux builders (probably the CPython ones).