TEZ-4492 : Approach 1 : Update Bower Registry to a different mirror

[AnmolSun]

This approach updates Bowerrc to use bower.herokuapp mirror to avoid Bower Registry CERT_EXPIRE issue

[tez-yetus]

🎊 +1 overall

Vote	Subsystem	Runtime	Comment
+0 🆗	reexec	1m 1s	Docker mode activated.
		_ Prechecks _
+1 💚	dupname	0m 0s	No case conflicting files found.
+1 💚	@author	0m 0s	The patch does not contain any @author tags.
		_ master Compile Tests _
		_ Patch Compile Tests _
+1 💚	whitespace	0m 0s	The patch has no whitespace issues.
		_ Other Tests _
+1 💚	asflicense	0m 52s	The patch does not generate ASF License warnings.
		2m 33s

Subsystem	Report/Notes
Docker	ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-284/1/artifact/out/Dockerfile
GITHUB PR	#284
Optional Tests	dupname asflicense
uname	Linux 02f41be7f301 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Build tool	maven
Personality	personality/tez.sh
git revision	master / 249e017
Max. process+thread count	46 (vs. ulimit of 5500)
modules	C: tez-ui U: tez-ui
Console output	https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-284/1/console
versions	git=2.34.1 maven=3.6.3
Powered by	Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

[amanraj2520]

+1 LGTM

[ayushtkn]

LGTM. The solution is mentioned over here as well
bower/registry#304 (comment)

Another solution is set strict-ssl as false, not sure if it is any better.

@abstractdog can you please bless this, the builds are failing due to this :)

[abstractdog]

yay, makes sense, thanks @AnmolSun, I'll merge this once github actions passed