Traffic Portal configuration option for Delivery Service active flags

[ocket8888]

This PR adds a new configuration option for Traffic Portal that allows exposing the new DS Active flag states. Disabled by default.

---

Which Traffic Control components are affected by this PR?

• Traffic Portal

What is the best way to verify this PR?

Set exposeInactive in the Traffic Portal Properties file to false and true and make sure each respective behavior works as expected.

PR submission checklist

• This PR doesn't need tests
• This PR doesn't have documentation because TP configuration options are not documented
• This PR has a CHANGELOG.md entry
• This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY

[mitchell852]

Can you help me understand what this does @ocket8888 ?

exposeInactive = true will display 3 options? active, primed, AND inactive
exposeInactive = false will display 2 options? active, primed but NOT inactive

^^ is that correct?

[rimashah25]

Can you help me understand what this does @ocket8888 ?

exposeInactive = true will display 3 options? active, primed, AND inactive exposeInactive = false will display 2 options? active, primed but NOT inactive

^^ is that correct?

While reviewing and testing, this is what I noticed:
exposeInactive= true, displays (expected with APIv5)

exposeInactive= false displays (as we see today)

[ocket8888]

The old notion of "inactive" is what is known as "primed" in APIv5. True "INACTIVE" is not available prior to that version, so when exposeInactive is true, it'll show all three Active States, and when it's false it'll show ACTIVE and PRIMED - but PRIMED will be labeled "Inactive".

[rimashah25]

Code LGTM.
Tested the configurable variable exposeInactive for both values: true & false and the dropdown for DS Active Flag changes accordingly.

[zrhoffman]

It would be nice to have some test coverage for this, but I won't hold up the PR for it.

[mitchell852]

@ocket8888 - arent there a bunch of DS tables as well that will still say "primed"?