Restructure the project to keep it sync with the upstream batch-tck

[liweinan]

Currently this project contains some manually maintained pom.xml files

• https://github.com/jberet/jberet-tck-porting/tree/main/src/main/resources

These pom files are used to replace the ones in the upstream project during JBeret TCK testings (both SE and EE TCKtestings):

• https://github.com/jakartaee/batch-tck

It's better to restructure this project to make it similar to the upstream project structure:

weli@mini:~/w/batch-tck|master⚡?
➤ ls -l                                                                                                                                                                                                                                        00:19:02
total 104
-rw-r--r--  1 weli  staff   1462 Apr  2 15:54 CONTRIBUTING
-rw-r--r--  1 weli  staff  11358 Mar 12 23:27 LICENSE
-rw-r--r--  1 weli  staff    967 Apr  2 15:54 NOTICE
drwxr-xr-x  6 weli  staff    192 Aug 10 02:52 com.ibm.jbatch.tck
...
drwxr-xr-x  7 weli  staff    224 Aug 10 02:52 com.ibm.jbatch.tck.exec
drwxr-xr-x  3 weli  staff     96 Aug 10 02:52 com.ibm.jbatch.tck.sigtest.exec
...
drwxr-xr-x  6 weli  staff    192 Aug 10 02:59 jakarta.batch.arquillian.exec
drwxr-xr-x  4 weli  staff    128 Aug 10 02:52 jakarta.batch.arquillian.exec-parent
...
-rw-r--r--  1 weli  staff  29768 May 15 01:56 pom.xml
weli@mini:~/w/batch-tck|master⚡?

This way the pom.xml files can be compared with the upstream files more conveniently, thus it can make future maintenance and dependencies update work easier.