Use lychee new cache-exclude-status option and upgrade lychee-action

[dmathieu]

Lychee's cache-exclude-status option has shipped. So we can use it rather than ignore 429s.
This also upgrades lychee-action to 2.1.0. We had to revert that in #6229 due to a regression, which was fixed in lycheeverse/lychee-action#255

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.8%. Comparing base (5b9cf72) to head (01e63e0).
Report is 1 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #6323   +/-   ##
=====================================
  Coverage   66.8%   66.8%           
=====================================
  Files        193     193           
  Lines      15580   15580           
=====================================
+ Hits       10408   10414    +6     
+ Misses      4881    4877    -4     
+ Partials     291     289    -2     

see 1 file with indirect coverage changes

[pellared]

@dmathieu

can we somehow get rid of:

* [429] [https://github.com/open-telemetry/opentelemetry-go/commits/main](https://github.com/open-telemetry/opentelemetry-go/commits/main) | Cached: Error (cached)

or does it mean that it still does not work as expected?

[dmathieu]

I think that means it works as expected. We currently cache 429s, and this PR uses the cache.
Once the cache is renewed, 429s won't be cached anymore, and they will be retried.

[pellared]

Once the cache is renewed, 429s won't be cached anymore, and they will be retried.

I am just not sure if the cache would be ever renewed given the cached error. Still, not a blocker. I think we can merge this PR.

[dmathieu]

The cache has a finite duration. It is renewed every day.