Fix up tests

[connersaeli]

This is identical to #390 (see writeup in that PR). There was an issue with my CircleCI account where it was running the tests under my own account and not under the ubccr account. I made a config change that resolves the issue, but it requires a new PR to apply the change.

Description

Motivation and Context

Tests performed

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project as found in the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[aaronweeden]

Why logoutDashboard instead of just logout?

[aaronweeden]

I see, because this is testing the internal dashboard. I would recommend authenticateDashboard instead of authenticate then.

[connersaeli]

So after a little bit of digging, it seems that the logout/authenticate (without Dashboard) is probably more desirable here. The authenticateDashboard does not work for these REST calls because even though they are in the internal dashboard, endpoints tested here such as supremm_dataflow/dbstats are part of the new REST stack. I need to double-check, but it seems that the {logout,authenticate}Dashboard does not properly authenticate the user for the required REST calls.

[aaronweeden]

In DashboardSupremmTest, Instead of logging out at the top of functions, I would recommend that for each call to authenticate there is a corresponding call to logout that happens after the request(s) have been made. In most cases, the logout would be after a single call to get, except for testResourceEnableDisable in which it would be after the three calls to get. The goal would be that each test resets the state back to where it found it.