Use cache on lint action

[kian99]

Description

This PR adds linting to the cache.yaml action so that a lint cache is available on the default branch for PRs to have a hot cache.

It also enables caching on the go-setup action in linting workflow, although this could cause a similar issue to #1307, a cache is not created if an existing cache exists so this shouldn't cause any issues.

[SimoneDutto]

i am curious, if i rerun the ci action w/o changing the code how well the linting is cached? or is it just for the deps?

[kian99]

@SimoneDutto

i am curious, if i rerun the ci action w/o changing the code how well the linting is cached? or is it just for the deps?

Run 1: No go cache, no lint cache, 12m40s
Run 2: Go mod cache, no lint cache, 4m29s
Run 3: Go mod cache, lint cache, 1m14s

Most of the time in the last run was spent restoring the mod cache.

[ale8k]

Think I'm confusd with how this works and maybe a chat at standup to explain it to me would help, just so I'm clear how the caching works... I'll have a read too

[SimoneDutto]

We can discuss it further in the standup but i give you a primer.

With go-setup you have a setup and a teardown step in your workflow.
The first is at the start and searches for a go cache in github cache and retrieves it, the second is done at the end of the workflow and stores go cache folders into github cache.

Go build step populates the cache with artifacts and deps and the linting step adds linting artifacts to the cache as well.

[kian99]

An important read to fully understand things is here https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows

[SimoneDutto]

@SimoneDutto >i am curious, if i rerun the ci action w/o changing the code how well the linting is cached? or is it just for the deps?

Run 1: No go cache, no lint cache, 12m40s Run 2: Go mod cache, no lint cache, 4m29s Run 3: Go mod cache, lint cache, 1m14s

Most of the time in the last run was spent restoring the mod cache.
nice!