Automatically set up cache

[thomaseizinger]

Given that this is a composite action, should we automatically set up a cache for it? It is effectively a no-op if users don't pass --cache but will benefits users that want to have one because they don't need to set it up manually then?

[mre]

I wouldn't mind. Sounds like a reasonable idea. @thomas-zahner @Arteiii what do you think?

[Arteiii]

I don't see an issue with this at all, as long as there's an option to fully disable the cache. Only disabling --cache might still create GitHub caches, which could cause problems in some setups

[mre]

Took a stab at it in #292.

[thomaseizinger]

Awesome! I was going to try and implement this but you beat me to it :)

[thomas-zahner]

I'm not experienced with lychee-action, but I don't see any problems and I agree that the feature makes sense.

[mre]

Okay, the plan is:

1. test the changes thoroughly by using the tag like so

   - name: Link Checker
     id: lychee
     uses: lycheeverse/lychee-action@cache
     with:
       fail: false

2. merge this and release version 3.0 once we're confident it works as expected