CMR-10009: Fix job-router load balancer referencing issues

[TylerHeald1]

Overview

What is the feature/fix?

If some infrastructure change causes the LB to be remade with the same name, it might not have the same DNS name, which requires job-router to need it's variables updated

What is the Solution?

Changed job-router to use the name of the LB to query AWS for the DNS name, so it isn't reliant on a more-likely-to-change value

What areas of the application does this impact?

job-router

Checklist

• [x ] I have updated/added unit and integration tests that prove my fix is effective or that my feature works
• [x] New and existing unit and int tests pass locally and remotely with my changes
• [x ] I have removed unnecessary/dead code and imports in files I have changed
• [x] I have performed a self-review of my own code
• [x ] I have commented my code, particularly in hard-to-understand areas
• [x ] I have made corresponding changes to the documentation
• [x ] My changes generate no new warnings
• [x ] I have cleaned up integration tests by doing one or more of the following:
  • de-duped, consolidated, removed dead int tests
  • transformed applicable int tests into unit tests
  • refactored to reduce number of system state resets by updating fixtures (use-fixtures :each (ingest/reset-fixture {})) to be :once instead of :each