Fix dist and reference doc coordinates setup

[manovotn]

Another set of changes needed for the release under new coordinates.

[manovotn]

This is one of the files that are included as part of the porting package we generate.
Its contents seem to be taken from Weld's code and among those files is this one offending file that doesn't have any license.

I don't think we should check either of these files but rat plugin didn't seem to accept any expression I tried so I ended up excluding just this particular file which works 🤷

[Ladicek]

LGTM, although I don't quite understand why we include Weld/WildFly-specific code here. Any explanation?

[manovotn]

LGTM, although I don't quite understand why we include Weld/WildFly-specific code here. Any explanation?

I don't remember why it was done so but Weld parts are used a reference example of how you run the TCKs so I suppose the TCK distribution comes with those so that you can try it locally.
There are scattered notions of it in the TCK docs, such as:

• https://jakartaee.github.io/cdi-tck/#arquillian-settings
• https://jakartaee.github.io/cdi-tck/#_example_weld_test_suite_runner
• https://jakartaee.github.io/cdi-tck/#_the_tck_environment

Frankly, I suppose much of this information is going to reference old artifacts or be plain out of date (like using WFLY 22 :)).

[Ladicek]

It's probably just me, but I would get rid of all that. We can just add, to the TCK documentation, some links to where the TCK runner is configured, for example in Weld and in WildFly.