Restore the EL javatest based branch , move EL standalone tck module to el-tck

[alwin-joseph]

Related Issue(s)
#1380

Describe the change

• Move the current refactored EL standalone tck module to el-tck (This source was used to release EL TCK 6.0.0 and 6.0.1 versions for EE11)
• Restore the el module based on the javatest classes to be run for platform. The new tests and the test related changes made in standalone el-tck EE11 are copied to the el/ EE module. This is needed to be able to update the EL platform tests using the tools tck-rewrite effort to run in servlet and jsp vehicles.

This will essentially create 2 sources of truth for EL tests - one for standalone and another for platform in EE11 - similar to the jms changes in #1395.

cc @scottmarlow @starksm64 @gurunrao

[scottmarlow]

@arjantijms please approve this change after reading the description. I would like to see your approval since you are the lead of the Expression Language specification.

[arjantijms]

@scottmarlow looks good, thanks!

[scottmarlow]

@scottmarlow looks good, thanks!

@arjantijms just one more point that may not be obvious to all. The component/standalone folder el-tck will retain all prior (Jakarta EE 8 - now) EL TCK commits but the new el folder history will start from this pull request.

The el tests will extend com.sun.ts.lib.harness.ServiceEETest. If we could made the el tests extend both com.sun.ts.lib.harness.ServiceEETest and the component el-tck test class, we would NOT need this fork.

[scottmarlow]

The el tests will extend com.sun.ts.lib.harness.ServiceEETest. If we could made the el tests extend both com.sun.ts.lib.harness.ServiceEETest and the component el-tck test class, we would NOT need this fork.

I have some ideas for instead using delegation but we are trying to meet a deadline for EE 11...