Add CI, pre-commit, prerelease and dependabot

[vatanaksoytezer]

This PR adds:

• Industrial CI that will run every PR and push to ensure robustness
• pre-commit to check cmake and file formatting as well as spelling.
• pre-release to run an isolated build before releases
• dependabot to keep up to date with Github Action changes. (@lauralindzey you may need to add dependabot to apl-ocean-engineering to get this working actually)

Suggest reviewing commit by commit:

• Add CI, pre-commit, prerelease and dependabot
• pre-commit changes: all these changes are automated, except for the changes in Contrbuting.md.

[lauralindzey]

I'm not familiar with dependabot at all -- can you tell me how to test this (you mention needing to make sure to add it to the repo?) either in the conversation for the PR or as an addendum to Contributing.md?

[vatanaksoytezer]

Dependabot is a bot that automatically opens PR to this repository when an action in CI has an updated version (pushes to its own branch in repo, thus needs write access).

[lauralindzey]

when an action in CI has an updated version

This is the bit I don't understand -- I'm used to using Github's CI tools to check if a branch passes tests before merging a PR.

What workflow are you automating here that would result in PRs?

[vatanaksoytezer]

It updates versions of CI tools automatically as in https://github.com/vatanaksoytezer/hydrographic_msgs/blob/vatan/ci/.github/workflows/ci.yaml#L39. Example PR from moveit: moveit/moveit2#1713

[lauralindzey]

Similarly, I'm not familiar with industrial_ci. Is there a way to check that it's working before I merge? Or do I have to merge for Github to automatically run it?

[vatanaksoytezer]

Hmm, you might need to enable Github Actions through organization. It works in my fork, see vatanaksoytezer#2.

[vatanaksoytezer]

To enable Github Actions: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository

[vatanaksoytezer]

Also please use squash merge when merging PRs, it would squash all the commits into a single commit thus we don't actually need to care about commits. History will be pretty clean this way. You can find this option on the little down button near the merge pull request button.

[lauralindzey]

OK, I'll check CI status here after merging; actions should be enabled.

And I'll squash the commits for this one =)