Fix self-referential dependencies when publishing test fixtures

[StefanBratanov]

PR Description

As suggested by @jframe

bratkartoffel/security-jwt@48a7e84

Fixed Issue(s)

N/A

Documentation

• I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

• I thought about adding a changelog entry, and added one if I deemed necessary.

[rolfyone]

LGTM

[Nashatyrev]

Relates to #7444

There are two points about this fix:

1. It returns back publishing test-fixture artifacts which is good
2. It returns back needless extra dependencies (derived from test-fixture scope) for the main artifact

I don't actually see any crime regarding the (2) except a bunch of unused dependencies are to be downloaded and appended to the classpath.

[StefanBratanov]

Relates to #7444

There are two points about this fix:

1. It returns back publishing test-fixture artifacts which is good
2. It returns back needless extra dependencies (derived from test-fixture scope) for the main artifact

I don't actually see any crime regarding the (2) except a bunch of unused dependencies are to be downloaded and appended to the classpath.

Didn't realise about (2) annoying really, we will see if there is another workaround, but given we actually have downstream consumers using the test-fixtures it is preferrable to be published.