Iterate and improve local development Testing and Linting

[radsec]

Prior to #89, a custom container was created to match the CI process for linting.

This issue is to track the iteration on how to enhance local developer testing and linting.

Current proposals:

• Custom container logic with GH Actions --> note, not everything here is supported and active issues exists
• Establish linting and testing with bazel natively --> it already can run unit tests, we could add a provider to run the linting

[discentem]

not everything here is supported and active issues exists

Can you unpack this a bit? What isn't supported in the docker containers and what active issues are you referring to?

[discentem]

Chatted with @radsec offline. Their concerns with custom containers for each Github Action is as follows:

• It's not clear on the surface how we can save the bazel cache between builds
  • Possible solutions: unknown right now
• We were not caching Docker layers so certain CI jobs that should be very fast (lint) were not fast.
  • https://evilmartians.com/chronicles/build-images-on-github-actions-with-docker-layer-caching