Use recommended policy-based authorization for Org Admin and Server Admin pages.

[bitbound]

This started as fixing the Server Logs page. The loading screen wasn't showing initially, because the LoaderHarness needed to register for events earlier in the component lifecycle.

Then wanted to fix one of the many tech debt items that have been bothering me for a while. The pages requiring Org Admin and Server Admin rights (derived from AuthComponentBase) were conditionally including/excluding content directly in the page based on the current user.

I changed these pages to use the recommended policy-based authorization approach, and added them to the pages Authorize tag. This lets the AuthorizeView in the app's router handle authorization for all the pages and displays the same template when not authorized.

Also fixed a bug causing the device to not update on heartbeat.

---

Please read the following. Do not delete below this line.

Thank you for your contribution to the Remotely project. It is required that contributors assign copyright to Immense Networks so we retain full ownership of the project.

This makes it easier for other entities to use the software because they only have to deal with one copyright holder. It also gives me assurance that we'll be able to make decisions in the future without gathering and consulting all contributors.

While this may seem odd, many open source maintainers practice this. Here are a couple well-known examples:

• Free Software Foundation: http://www.gnu.org/licenses/why-assign.html
• Microsoft: https://cla.opensource.microsoft.com/

A nice article on the topic can be found here: https://haacked.com/archive/2006/01/26/WhoOwnstheCopyrightforAnOpenSourceProject.aspx/

By submitting this PR, you agree to the following:

You hereby assign copyright in this PR's code to the Remotely project and its copyright holder, Immense Networks, to be licensed under the same terms as the rest of the code. You agree to relinquish any and all copyright interest in the software, to the detriment of your heirs and successors.

[colinblaise]

Is is correct to not specify a policy here?

[bitbound]

Yeah. The default policy for the Authorize attribute is "IsAuthenticated". So you can add just the attribute like this to anything that requires the user to be logged in, but nothing else.