VCR: Allow configuration of revocation list max-age

[reinkrul]

Fixes #3991

[qltysh]

Coverage Impact

⬆️ Merging this pull request will increase total coverage on master by 0.01%.

Modified Files with Diff Coverage (4)

Rating	File	% Diff	Uncovered Line #s
	vcr/cmd/cmd.go	0.0%	44
	vcr/vcr.go	100.0%
	vcr/revocation/types.go	100.0%
	vcr/revocation/statuslist2021_verifier.go	100.0%
	Total	80.0%

🤖 Increase coverage with AI coding...

In the `vcr-configure-revocation-maxage` branch, add test coverage for this new code:

- `vcr/cmd/cmd.go` -- Line 44

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.

[stevenvegt]

How does this relates to the validUntil param of the status list itself? This value should imho be credential specific because it really depends on the governance of the credential. If the issuer promises to update the list at least once a week, there is no need to fetch this every time after 15 minutes. Right?

If it is merely a demo/dev thing, perhaps scope it like that and don't allow it in strict-mode?