[appserver-jersey] Added Docker setup, updated tests & CI, liquibase

[mpgxvii]

• Adds support for email notification transmission for the appserver Jersey
• Fixes failing integration tests for the appserver Jersey.
• Separated jersey updates from Added Docker and email transmission setup, corrected tests #544 by @this-Aditya
• Appserver Jersey Main and Release Workflow (From Added CI Setup and Integration Tests for Microservices #545) by @this-Aditya
• Liquibase fixes (Add Liquibase support and legacy -> Jersey DB migration #548) by @this-Aditya

[this-Aditya]

Hi @mpgxvii, thanks for the PR -- I diffed appserver-jersey/ between this branch and 36c77ff, the last commit in the #542 → #551 chain that still has the jersey module, and there is newer work here that isn't in the chain at all, but some files differ and a few fixes from #550 and #551 is not synced.

Changes from 75cfe4d from #551, "Make Quartz DB-backed and compatible with legacy-scheduled jobs", is missing. QuartzSchedulerFactory is back to a StdSchedulerFactory(), which is an in-memory RAMJobStore, so scheduled notifications don't survive a restart. SchedulerConfig doesn't have JDBC settings and the quartz: block in appserver.yml. MessageJob also moved back under ...jersey.service.quartz. It was kept in the legacy package because Quartz stores the class name in QRTZ_JOB_DETAILS.JOB_CLASS_NAME, so jobs written by the Spring app server won't resolve anymore.

Rest of what I found:

What	Where	From
checkPresence(doesntExists, ...) never fires, checkPresence only throws on null and this is a non-null Boolean	TaskService.kt	0f4872d from #550
Missing return after the "no email address" warning, so it tries to send anyway	EmailTransmitter.kt	804d699 from #550
Permission checked against token.subject instead of fcmUserDto.subjectId	UserResource.kt	804d699 from #550
Two leftover debug println calls in updateProject	ProjectService.kt	804d699 from #550
Path is /filter, legacy uses /filtered	FcmNotificationResource.kt	79af7dc from #550
SUBJECT_READ on the GETs, legacy uses UPDATE	TaskStateEventResource.kt	79af7dc from #550
schedule param defaults to false, chain has true	FcmNotificationResource.kt	79af7dc from #550
Lost @CollectionTable(name = "notification_additional_data")	Notification.kt	89d26ff from #551
Lost joinColumns = [JoinColumn(name = "data_message_id")]	DataMessage.kt	4549aca from #551
Still on the rigid HH:mm:ss.SSSXXX pattern instead of HH:mm:ss[.SSS]XXX, this is what broke the integration tests last time	ProjectDto.kt, FcmDataMessageDto.kt, FcmUserDto.kt	f875477 from #551
Swagger UI dropped, Enhancers.swagger(...) plus @Tag on all 8 resources	AppserverResourceEnhancerFactory.kt	abe7bcf from #550
Dropped Task.equals/hashCode and the LinkedHashSet in the two repeat handlers. The PersistenceException catch here only dedups notifications, not tasks	Task.kt	ac85c63 from #550
radarJerseyVersion down from 0.12.7 to 0.12.2	Versions.kt	0a91a03 from #551

I noticed but wasn't sure about, they may be deliberate. Task.kt uses GenerationType.AUTO where the chain and legacy both use SEQUENCE.

[mpgxvii]

@this-Aditya Thanks for double checking. It seems that the newest changes (db-quartz) did not get pulled so the changes were not added here. I've added the latest commits now.

[this-Aditya]

LGTM, Thanks @mpgxvii