…l with dependencies specified by Cargo.lock files of the installed package.

…rsion 1.0 (#6246)

* Motivation for features / changes
As requested and noted in #6197, we can bump this restriction, which is
currently affecting compatibility of TB with dependency requirements
from other packages. After the OOB auth flow migration, this should be
possible.

* Technical description of changes
Just bump the restriction for `google-auth-oauthlib` in our
`requirements.txt` file, to support newer versions.

* Detailed steps to verify changes work correctly (as executed by you)
Executed the auth flows (both the console-only one, and the one that
uses a browser in the same machine), and validated that they work as
before with the newer version.

…2.11.2)

* Motivation for features / changes

I found a couple of problems with scalar line chart rendering in Safari
while investigating
#6280.

* Safari 16.4 introduced limited OffscreenCanvas support. Notably it
does not include 'webgl2' support. We have to be a bit more strict with
our OffscreenCanvas feature detection to check for 'webgl2' support.
* Scalar line charts still would not render in either canvas or svg mode
until the charts were resized manually. We have to adjust our CSS in
order to convince WebKit to render the line chart with the space
available to it. We use 'flex' for this.

* Testing

  I tested in both Safari and Chrome that Canvas/Three.js and SVG
rendering work (using forceSVG=false and forceSVG=true, respectively).

  I imported the changes internally and ran internal presubmits.

  I did not write any more tests because (1) utils.ts is currently not
covered by tests and (2) this is a Safari problem which only has best
effort support.

…part of the nightly build (#6332)

* Motivation for features / changes
 Nightly Build broken after the pip 23.0->23.1 release

* Technical description of changes
Found a newer version of the docs repo that doesn't exhibit the error
and pinned to that version of the repo.

* Screenshots of UI changes
none
* Detailed steps to verify changes work correctly (as executed by you)
Creating the PR and seeing if it triggers the new workflow, in flight.

* Alternate designs / implementations considered
none