Extract "common" package do a separate jar

[oridag]

Some of the runtime and compiler dependencies may conflict with other dependencies (in my case antlr and protobuf) so in some cases it is required to wrap the compilation and evaluation API in an external service. In this case it is helpful to have a minimum-depenedncy module that can be loaded in the client, which have for example the error codes enum, and the code to builds and manipulates ASTs

[l46kok]

This has been on my radar for a while, for reasons such as https://jlbp.dev/JLBP-5 (ex: dev.cel.common.CelAbstractSyntaxTree is included in both compiler/runtime jars). But yes, we're eventually aiming to publish //common as its own jar with minimal dependencies and without duplicated classes across. Things like //parser will continue to take a hard dependency on ANTLR, but hopefully a common jar will alleviate the issue here.