Add an automated check for used batch compiler version

> If I understand it right, jdt core should have strict dependency relationship with batch compiler. It can be a range too, but range should set minimal ecj version to latest "tested" one. On beta branch it should be also higher as on master, isn't?

If there is going to be a tightly coupled dependency between jdt.core and batch compiler, this information needs to be documented as some place so that who ever is updating the batch compiler version does not miss updating the version in the dependencies of jdt.core

_Originally posted by @ktatavarthi in https://github.com/eclipse-jdt/eclipse.jdt.core/issues/867#issuecomment-1476055729_

The best documentation would be an automated test. The test should check that required and reexported batch compiler version in jdt core matches latest batch compiler version in master.

Start by locating jdt.core's dependency declarations and the batch compiler version used on the master branch. Done means an automated test verifies that jdt.core's required and reexported batch compiler versions match the latest batch compiler version in master.

Written by the indexing model from the issue text.