Lighthouse CI for performance and accessibility

[krowvin]

Fixes #561

Solution

Uses gradle to spinup a local server using existing src and then runs the lighthouse CI in a sep task against that temporary service. Writes the output files to disk locally. Will attempt to update/test CI/CD further before submitting. But hoping to

1. Only run tests if the web-ui files have changed
2. Block PR if a 508 / performance issue is found (if the score is < 95%)
3. Load output to artifacts for viewing if a user prefers CI/CD for testing

how you tested the change

Tested on windows/macos

Pull down, run
.\gradlew a11yScan

[MikeNeilson]

generally reasonable, needs a few organization and gradle tweaks which i can pr to this pr for.

[krowvin]

The CI/CD is hanging waiting for the server. I was using act locally to try and figure that out.

I also tried to figure out how to dynamically determine URL, as well as, logging in.

Might be able to list files in the web app dir since they are static and run lighthouse on those paths.

For the login, I found a puppet library to add a middleware for login but did not get the chance to actually test.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud