Update periodic-links-checks, add maxHistory for Helm runner

[mszostok]

Description

Currently on cluster, we have 232 Helm release secrets. Unfortunately, the Helm runner upgrades Helm release with maxHistory parameters set to 0 which means no history limit. This causes, kubed to crash as we have limit to 100mb and kubed to sync Secrets and ConfigMaps fetch all of them. Unfortunately, we cannot narrow down the fetched secrets.

Running helm upgrade cmd locally reduce the history to 3 latest releases:

 ▲ helm upgrade cert-manager ./deploy/kubernetes/charts/cert-manager -n capact-system --reuse-values --history-max 3
 ▲ helm history cert-manager
REVISION	UPDATED                 	STATUS    	CHART                     	APP VERSION	DESCRIPTION
32      	Mon Oct  4 14:20:29 2021	superseded	cert-manager-0.5.0-f6cea95	           	Upgrade complete
33      	Fri Oct  8 08:39:30 2021	superseded	cert-manager-0.5.0-f279dd9	           	Upgrade complete
34      	Mon Oct 11 12:43:03 2021	deployed  	cert-manager-0.5.0        	           	Upgrade complete

Changes proposed in this pull request:

• Update periodic-links-checks.yaml to run only on weekdays
• Add option to specify MaxHistory for Helm runner (default 10)

Related issue(s)

• Periodic tests on long-running cluster are failing #532