ui: Added informative warning for insufficient privileges

[nathanstilwell]

Previously, /#/reports/nodes would seem to hang in a loading state
indefinitely when a DB Console user wouldn't have admin privileges for
that endpoint. This was due to nodes data being empty from a 403
response.

An error is captured in the application state for this response, so
mapping this error as a prop to the component, the UI can distinguish
between the nodes data simply being empty and being empty due to a
restriction error.

Detecting this error, we render an <InlineAlert /> to notify the user
of their lack of privileges.

Release note (ui change): All Nodes report notifies user is they need
more privileges to view information.

[cockroach-teamcity]

This change is 

[thtruo]

@nathanstilwell could we also include a backport into 21.1 and 20.2? Given that David's endpoint changes were backported to the same versions, we should do the same here

[Santamaura]

Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @dhartunian)

[nathanstilwell]

@thtruo Perhaps I've lost the plot with backporting, but doesn't this PR need to be merged before I can backport the change to release branches?

[Santamaura]

@nathanstilwell I believe you can add backport labels and blathers will auto create them after this is merged

[thtruo]

Perhaps I've lost the plot with backporting, but doesn't this PR need to be merged before I can backport the change to release branches?

Sorry @nathanstilwell I jumped the gun, didn't realize this was the case

I believe you can add backport labels and blathers will auto create them after this is merged

TIL!

[nathanstilwell]

@thtruo It turns out you are right! I haven't reviewed our backporting docs in a while and things seem much better now. 😄

Thanks for the nudge in the right direction @Santamaura

[nathanstilwell]

bors r+

[craig]

Build succeeded:

• GitHub CI (Cockroach)

[blathers-crl]

Encountered an error creating backports. Some common things that can go wrong:

1. The backport branch might have already existed.
2. There was a merge conflict.
3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.

---

error creating merge commit from 3b4274d to blathers/backport-release-20.2-71960: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 20.2.x failed. See errors above.

---

error creating merge commit from 3b4274d to blathers/backport-release-21.1-71960: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 21.1.x failed. See errors above.

---

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.}