Alternative Standalone Sampler

[jtulach]

Continuous work on enso-org/enso#3389 has revealed that it is not possible to exclude five NetBeans libraries when using sampler module standalone. To address that this PR continues in #4047:

• d66ce57 duplicates the tests to check not only the InternalSampler, but also existing CLISampler
• 9f4ec39 adds yet another StandaloneSampler and its test

The test creates own ClassLoader and loads just the sampler JAR, without dependencies on other NetBeans modules (so Lookup isn't available) and then performs the AbstractSamplerBase tests. This guarantees that all three samplers behaves the same.

It'd be ideal if these changes could be uploaded to Maven central soon, as enso-org/enso#3389 can only consume released binaries.

[neilcsmith-net]

Curious why this is going into delivery and not master?

[ebarboni]

I accepted #4047 no more thinking on just accept bug fixes.
I merge this one as works for me + green and merge rc2

[JaroslavTulach]

Curious why this is going into delivery and not master?

I need Maven bits, so I'd like to get this into NetBeans 14.

[matthiasblaesing]

Curious why this is going into delivery and not master?

I need Maven bits, so I'd like to get this into NetBeans 14.

I think the point that @neilcsmith-net was trying to make is, that this does not look like a PR helping to stabilize NB14. The description of the issues shows IMHO that these are feature changes, so that another dependency gets a lower number of dependencies.

[neilcsmith-net]

Yes, exactly what @matthiasblaesing said! This doesn't seem to fit the normal criteria for merges to delivery. Not that there's a problem with bending the rules occasionally, just like to see the reasoning (cost/benefit) in the PR for doing so.