Allow MIT-0 Licence

[JackPGreen]

The org.reactivestreams:reactive-streams:1.0.4 transitive dependency uses an MIT-0 licence, which was not specifically allowed in the license-maven-plugin configuration.

reactive-streams has been on MIT-0 for a long time, but only since #25284 - where the S3 client was updated to use new reactive-streams - has this become a problem.

This caused intermittent failures of the PR builder.
This intermittency was presumably caused by the fact that the licence check was recently turned off by default for performance reasons (see comments on the license.skipAddThirdParty property).
Although the original PR builder execution failed the first time with this error, the second time it passed and was merged - and then caused more PR builder execution failures on other, unrelated PRs.
Unfortunately I don't have a solution on how to prevent this problem in future.

As MIT-0 is a less restrictive version of the MIT licence (which is included), so I've included this also.

[nishaatr]

Is MIT-0 a valid SPDX identifier?
I created guide to help when updating 3rd party license.
Please check https://hazelcast.atlassian.net/wiki/spaces/EN/pages/4595122178/How+to+fix+Hazelcast+THIRD-PARTY+license+issues

[JackPGreen]

Is MIT-0 a valid SPDX identifier? I created guide to help when updating 3rd party license. Please check https://hazelcast.atlassian.net/wiki/spaces/EN/pages/4595122178/How+to+fix+Hazelcast+THIRD-PARTY+license+issues

Yes.

[nishaatr]

Is MIT-0 a valid SPDX identifier? I created guide to help when updating 3rd party license. Please check https://hazelcast.atlassian.net/wiki/spaces/EN/pages/4595122178/How+to+fix+Hazelcast+THIRD-PARTY+license+issues

Yes.

Yes it is. just checked.
Optional: As per guide best to create a license merge entry so its easier for next time to merge any mis-named MIT-0 license

[JackPGreen]

Is MIT-0 a valid SPDX identifier? I created guide to help when updating 3rd party license. Please check https://hazelcast.atlassian.net/wiki/spaces/EN/pages/4595122178/How+to+fix+Hazelcast+THIRD-PARTY+license+issues

Yes.

Yes it is. just checked. Optional: As per guide best to create a license merge entry so its easier for next time to merge any mis-named MIT-0 license

I thought about this, but from what I understood, a merge entry is to help merge aliases of the same licence. As there's only label for MIT-0, there's no point doing that...?

[nishaatr]

Is MIT-0 a valid SPDX identifier? I created guide to help when updating 3rd party license. Please check https://hazelcast.atlassian.net/wiki/spaces/EN/pages/4595122178/How+to+fix+Hazelcast+THIRD-PARTY+license+issues

Yes.

Yes it is. just checked. Optional: As per guide best to create a license merge entry so its easier for next time to merge any mis-named MIT-0 license

I thought about this, but from what I understood, a merge entry is to help merge aliases of the same licence. As there's only label for MIT-0, there's no point doing that...?

Sure. np. I was just thinking for the next person tbh. If merge node is there it forces the next person to merge as opposed to possibly add the license to include block directly. We are good for now !!