* fixing syntax error
* changing the way we check the number of build status tries
* adding in the Crowdin Api Token env var to the main step
* Breaking up the Crowdin update step into smaller manageable steps
* fixing env var for the download step
* fixing build id env for download
* Fixing PR branch env vars
* adding in a different way of pushing if branch already exists
* fixing the git bot user
* Add CipherListVirtualScroll strategy
For use in cdk-virtual-scroll. Subclasses the default FixedSizeVirtualScroll
but reads the first available itemSize from the rendered content instead of
setting it in the template.
* Fix linting and style
* Refactor virtual scroll strategy
* linting and style
* Subclass virtual scroll strategy directive
* fix linting
* Fix filename conventions
* switching back to npm install because duo_web_sdk is in the package-lock.json as an ssh url
* trying the workaround found in https://github.com/npm/cli/issues/2610
* adding in the jslib to see if that fixes the original problem. Removing the workaround to isolate the solution
* adding in back the workaround
* updating the way we are deploying the web qa project
* adding double quotes to try to fix the new image tag
* trying the env var on a multi-line
* fixed the git ref image name in the build workflow
* fixing the the image tag in the qa deploy workflow
* adding in the k8s namespace to the set image
* Ensure business plan is selected for providers
* Show add organization button on if user has valid orgs to add
* Correct client owner description
* No drop down options if you can't manage organizations
* Style provider set up toast
* Correct translation strings
* Do not show provider organization management for non admins
* Product feedback for provider org description
* Correct message grammar
- `visibility:hidden` also hides text from assistive technologies, leading to the settings link lacking an accessible name when not hovered (focused with keyboard only, for instance)
- turn the styles around and hide the non-hovered link's span with "visually hidden" styles https://www.a11yproject.com/posts/2013-01-11-how-to-hide-content/
- also include `:focus` to make the text visible when hovered (for sighted keyboard users)
- more semantically accurate, will expose these as buttons to assistive technologies
- note: while having block-level elements like `<div>` inside a `<button>` is an html validation error, it does not affect functionality as long as there's no more structure inside it
