ci: add govulncheck-action

[mmatczuk]

No description provided.

[what-the-diff]

PR Summary

• Establishment of End-to-End Testing Workflow
  A new workflow has been set up devoted to performing end-to-end testing. This is an important step as it tests our system from start to finish, ensuring the whole process operates as expected.

• Removal of Previous Workflow File
  The previously used go.yml file was deleted. This could significantly declutter our workflow directory and also indicates a shift in our pipeline management process.

• Incorporation of Vulnerability Checking Workflow
  We have added an important routine to regularly check for any potential security vulnerability in our codes, improving the overall robustness of our system against malicious attacks.

• Addition of Linting Workflow
  A new workflow for linting has been introduced. Linting helps us maintain quality code by finding and fixing issues early, subsequently enhancing code readability and reducing the chances of encountering bugs.

• Creation of a Multi-Platform Testing Workflow
  A new workflow dedicated to running tests on various platforms was added. It allows our software to be more versatile and adaptable to different operating environments, increasing its usability for a broader set of users.

[Choraden]

Looking at a few of the latest run actions[1] I don't really see the time benefit.

Separate actions total duration:

• Test 1m 4s
• E2E 7m 13s
• Lint 23s

vs previous Go action total duration from 3 random runs:

• 7m 4s
• 8m 2s
• 7m 9s

If you like the jobs being separated I'm good with it, but as you can see Test and Lint jobs time contribution to Go action are negligible.

[1] https://github.com/saucelabs/forwarder/actions

[mmatczuk]

If you like the jobs being separated I'm good with it, but as you can see Test and Lint jobs time contribution to Go action are negligible.

It's just a beginning.

[mmatczuk]

But I think we could join lint and test.