* Pinning version of AST instead of using latest
* adding the pinned version of the commit
* adding an array join
* pinning version of dotnet
* trying the AST pin of the version we started using
* disabling jobs and adding test step to window job
* adding dotnet 2.1.x to see if that fixes the issue
* removing the test code and testing the addition of .net 2.1.x
* repinning to last successful sign
* trying the newest version of AST
* disabling the non-windows jobs again
* disabling the windows build job and added a test job
* removing stray comma
* changing the multiline delimiter
* pivoting away from our EV cert and testing with a test one
* switching back to the EV cert and adding a verbose flag
* disabling some steps that are breaking
* swithing back to the test cert
* testing new format for the ast command
* removing the node portions of the test since they are not needed
* trying AST without the tenat-id
* rolling back to original commit
* switching to custom AST for better troubleshooting
* removing the ast commit logic and forcing latest
* fixing up the pwsh sign command
* fixing the AST verison
* making sure that the secrets are not blank
* trying the EV cert for signing
* Using pinned commit from AST instead of custom code
* fixing env
* building the actually pinned commit instead of whatever the other thing was...
* testing the windows job
* removing the dotnet 2.1.x dependency since the older AST version shouldn't need it
* reenabling the test ast job since something is failing
* moving the git switch command
* testing new gh-action
* fixing the gh-action path
* updating the hash of the new action
* enabling the build jobs again
* updating the hash for the new Install AST action
* fixing linter issues
* Use separate modal for set pin
* Fix modal style and layout
* Minor fixes
* Remove incorrect label
* Fix initial focus and tab a11y
* Fix unrelated linting
* Update jslib
* Moving the web constants to the app config for more flexibility
* removing personal integrations from QA
* changing the PayPal Configuration setup to match the pattern in the services module
* removing the webConstants file after successful test
* renaming the braintree config key to something more understandable
* Fix canManagePolicies logic to include providers
* Move new logic to isOwner (same as server)
* Refactor policyAppliesToUser
* Use const instead of var
* Fix linting
* adding a file to the QA container to enable easy tracking the version of the currently deployed web client
* adding another visual representation of the QA version
I have a device that is blocking navigation (per chrome dev tools) on the success callback for reasons unknown. After comparing with the captcha connector (which works flawlessly), the only difference I can find is that captcha doesn't do anything else after `document.location.replace` for mobile. I'm not sure if this is the culprit but it can't hurt to try.
