Clarify the requirement to publish the TCK under the EF TCK Licence

The requirement to deliver a TCK under an open-source license as well as under the EFTL confuses some specification project teams.

We should clarify this further.

Currently we only say the following:

The Project Team must designate exactly one TCK under an Open Source License for each Specification Version of a Technical Specification. A binary version of the TCK licensed under the Eclipse Foundation TCK License becomes a part of the Final Specification.

Does this mean, for example, the final TCK must be released both with the open-source license and the EF TCK Licence?

Maybe we can re-write this to be more helpful, or add a note/tip. There's certainly an opportunity to do better in the operations guide.

/cc @ebratt