v0.41.0

What's changed

Open My work's GitHub pull requests in their ADO project, and scroll

The first test of the GitHub tab in the My work flyout showed the tab
does render, but its frame grew to fit every row, so the list ran off
the bottom of the flyout with no way to scroll and no footer. The frame
no longer resizes itself to its content: it fills the tab, the cards
scroll inside it and "View more" stays pinned at the bottom with a rule
above it, as on ADO's own Pull requests tab. If the flyout ever hands
the frame a small default height instead, it asks for a flyout-sized
one.

Rows used to open the pull request on github.com. They now open it in
our Pull requests hub, in the ADO project that connects the repository
(an Azure Boards GitHub connection), and the tab lists only pull
requests in repositories some project connects. When several projects
connect the same repository, a click opens a menu of those projects
(an azure-devops-ui ContextualMenu); the title's href is the first
project's page, so middle-click and "open in new tab" still work.

Finding those projects means listing the organisation's projects, which
needs the vso.project scope, so this release adds it. An organisation
administrator has to approve the new permission before this version
installs. Each project's connections are read six at a time and the
result is cached in the browser per organisation for 30 minutes, so the
flyout normally renders from the cache and refreshes in the background.
Without the scope the tab falls back to the project the page is in.
Search now asks for 100 results, because filtering happens afterwards.

Mock harness: a second project, "Platform", that also connects
customer-portal, a PR from a repository no project connects (which
must not show), and noProjectScope and noConnections scenarios.

_192e7b8

Full changelog: v0.40.0...v0.41.0