Many fixes

[juherr]

For review, comments and feedbacks

[missedone]

@juherr why rename the group ID? would it impact the CI build as the credentials may tie with group ID org.testng, we shall test out soon

[juherr]

It looks more commons to have all modules under the same groupId.
I don't remember why we didn't do it directly.

I think the delivery at central is the good time to change it.

The credentials are able to deploy everything under groupid org.testng or children.

[juherr]

Btw, feel free to cherry pick some commits because I'm not sure that all are a good idea.

[krmahadevan]

@missedone - So we are cherry picking the needed commits from this PR ? Please let me know.

[missedone]

Yes, changing the group ID and artifact ID may break several things, even though I assume only testng eclipse plugin use testng-remote, however, I think it's better to keep the compatibility in case somebody else uses it as well

[missedone]

@juherr @krmahadevan are you good with releasing 1.5.0 use current master HEAD?
(I need to test if the release github actions workflow works or not, no way to dry-run :) )

[krmahadevan]

@missedone - I am not that familiar with the testng-remote codebase to be able to answer that question.
So I would leave the decision to you :)

[juherr]

@missedone sure, go ahead