[v22.x backport] test: account for varied OpenSSL CCM final behaviours

[everett1992]

Backport of test: account for varied OpenSSL CCM final behaviours
(28b571c) from #65542, which landed via commit-queue-rebase, so the
test fix is one commit inside the OpenSSL 3.5.8 update rather than its own
PR.

It does not cherry-pick cleanly: main has hasOpenSSL(3) where this
branch still has hasOpenSSL3, and the block is not wrapped in an
if (!ciphers.includes('aes-128-ccm')) guard on this branch
(indentation only).

Why now

We build our Node distribution against our own OpenSSL rather than the
bundled copy, and we run the upstream test suite. We have just updated to
OpenSSL 3.0.22 (for v20.x/v22.x) and 3.5.8 (for v24.x/v26.x), so
parallel/test-crypto-authenticated is already failing on our v22.x and
v24.x builds. The same backport will be needed here if and when these
branches update the bundled OpenSSL.

OpenSSL 3.0.22 and 3.5.8 include openssl/openssl#32427. Before it,
ossl_ccm_stream_final() returned early when the payload update() was
skipped, so encryption produced no tag and decryption could report
success without verifying the supplied tag. With the fix, final() on an
empty CCM message succeeds and produces a real tag instead of failing
with ERR_OSSL_TAG_NOT_SET — which is what the test asserted
unconditionally.

Verification

Ran parallel/test-crypto-authenticated before and after this change on
Node 22.23.2 built against shared OpenSSL 3.0.22: fails before, passes
after. Also confirmed on 20.20.2 (OpenSSL 3.0.22) and 26.7.0 (OpenSSL
3.5.8).

AI disclosure

The conflict resolution and this description were drafted with an
agentic coding CLI. I ran the test before and after on the builds above
and read the OpenSSL change to confirm the behaviour it describes.

Companion backport for v24.x: #65710

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/76862/