Selenium test changes for Release 2.0

[rishagg01]

🗣 Description

Selenium test scripts were modified to enable the tests to be run again for Release 2.0

💭 Motivation and context

The Selenium tests were being skipped due to Release 2 architecture changes. The scripts have been refactored to enable them to run against the new dashboards.

📷 Screenshots (DELETE IF UNAPPLICABLE)

🧪 Testing

The tests were executed and they passed.

✅ Pre-approval checklist

• [Y] There is a gitIssue that this PR resolves
• [Y] Git Issue that this PR solves has been selected in the Development section
• [Y] The PR's base branch has been modified to be the proper branch.
• [Y] Changes are limited to a single goal AND
  the title reflects this in a clear human readable format
• [Y] Issue that this PR solves has been selected in the Development section
• [Y] I have read and agree to LME's CONTRIBUTING.md document.
• [Y] The PR adheres to LME's requirements in RELEASES.md
• [Y] These code changes follow cisagov code standards.
• [Y] All relevant repo and/or project documentation has been updated to reflect the changes in this PR.

✅ Pre-merge Checklist

• [Y] All tests pass.
• [Y] PR has been tested and the documentation for testing is above.
• [Y] Squash and merge all commits into one PR level commit.

✅ Post-merge Checklist

• [Y] Delete the branch to keep down number of branches.
• [Y] The PR is labeled with feat for an added new feature, update for an update, OR fix for a fix.
• [Y] The PR contains Resolves #<issue #> so that merging it closes out the corresponding issue. For example Resolves #132.