Cache after base run

[devKarpov]

No description provided.

[villiamriegler]

An alternative approach would be to pull the diff from the last push. This allows the program to look through less code. However, the current biggest bottleneck in performance is building dependencies every time in docker. Parsing comments is essentially instant in comparison, therefore this will be pushed until either we are able to speed up build time or we see significant time being spent on parsing. This could be if this action are to be used on a truly large repository. However, as the action runs in the background we are also able to take more time as the creation of issues does not block any other work and the issues will eventually appear as soon as the container image is built.