LTI 24.0.9: Improve ability to stay current with new versions of LSP4iJ.

[mrglavas]

The overall goal of this epic is to improve our ability to stay current with new versions of LSP4iJ.

LSP development for LTI 24.0.7:

• Migrate LTI from the embedded Microshed LSP4iJ to using the Red Hat LSP4iJ plugin from the IntelliJ Marketplace. (Update to use the lsp4ij from Jetbrains marketplace #608)
• Create and deploy continuous integration workflows which build and test LTI against the latest changes (PRs and pushes to main) to Red Hat LSP4iJ. Enhance LTI workflows with Slack notifications which inform the team of the success or failure of LSP4iJ continuous integration builds. (Continuous integration of the Red Hat LSP4iJ plug-in. #666)
• Automate monitoring of activity in the Red Hat LSP4iJ project, generating Slack notifications for new, updated and recently closed PRs. (Determine how we should activitely monitor changes being made to LSP4iJ. #802)
• Align LTI with versions of LSP4iJ, LSP4MP4iJ, LSP4MP which satisfy requirements for a release. (LTI 24.0.9: Align LSP4iJ, LSP4MP4iJ and LSP4MP for the release. #841)

Remaining LSP 24.0.8 development work, post-24.0.6:

• Once 24.0.6 is tagged for release, create a development branch from latest main.
• Integrate the latest Red Hat LSP4iJ release on this branch, applying required changes to LTI that were established in the proof-of-concept.
• Upgrade LSP4MP4iJ from Quarkus tools to the latest level that matches the chosen LSP4iJ release (current target is LSP4iJ 0.0.4).
• Integrate enhancements to the workflows for continuous integration and Slack notifications that were established in their proof-of-concepts.
• Stabilize the development branch, working with the community to resolve issues that need to be addressed before LTI can release.
• Once stable, merge the development branch back into main.

[TrevCraw]

All items complete.