[draft] ci: fix duplicate jobs

[davmacario]

Closes #47

📑 Description

• Prevent duplicate jobs - now Super Linter is only ran on pull requests
• Create new job to build and push Depthai Docker image to the GitHub Container Registry

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

ℹ Additional Information

The PR is still in draft, as I am trying to find a way to test the new job (I am accepting suggestions).

I also would like to trigger the action when, either:

• The files Dockerfile, requirements.txt and vision_webserver.py are changed when pushing (or merging) to main
• The file defining the job is changed regardless of the branch

but it does not seem to be possible (as I can only define the push trigger once). If there was a way to do so, it would also be possible to test this job without having to merge to main first.

[davmacario]

@gmacario I am open to suggestions :)

[gmacario]

@gmacario I am open to suggestions :)

Maybe reading the examples at https://github.com/super-linter/super-linter could help

[gmacario]

Concerning

I also would like to trigger the action when, either:
...

I am quite sure you are familiar with https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow, aren't you?

[davmacario]

I am quite sure you are familiar with https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow, aren't you?

I am now, and the documentation for the workflow_dispatch flag clearly says:

Note: This event will only trigger a workflow run if the workflow file is on the default branch.

Indeed, despite having pushed changes that add the workflow_dispatch condition, I am not able to manually trigger the action as it is not on the default branch.

[gmacario]

@davmacario Re:

• Create new job to build and push Depthai Docker image to the GitHub Container Registry (to be tested)

Although this feature is quite welcome, I would suggest to handle that in a separate PR since it is not related to bug #47 which this PR is supposed to fix

[davmacario]

@gmacario should work now

[gmacario]

With the caveat which I mentioned in #48 (comment)

@davmacario Re:

• Create new job to build and push Depthai Docker image to the GitHub Container Registry (to be tested)

Although this feature is quite welcome, I would suggest to handle that in a separate PR since it is not related to bug #47 which this PR is supposed to fix

LGTM. Merging PR