Revert Traffic Monitor renaming to rascal

[rimashah25]

We need to roll back Rascal changes until we can identify all the tools that expect Traffic Monitor to be Rascal. Users may have tools used internally that hard-code RASCAL which need to first change before these changes can be merged. So before changing it, we need to have a discussion on the mailing list to ensure everyone's okay with it.

---

Which Traffic Control components are affected by this PR?

• Documentation
• Traffic Control Cache Config (t3c, formerly ORT)
• Traffic Control Health Client (tc-health-client)
• Traffic Control Client
• Traffic Monitor
• Traffic Ops
• CDN in a Box
• Automation

What is the best way to verify this PR?

Run integration, unit test.
Ensure CIAB build correctly
TO API endpoints work as expected.
Clients (eg: T3C) work as expected.

If this is a bugfix, which Traffic Control versions contained the bug?

PR submission checklist

• This PR has tests
• This PR has documentation
• This PR has a CHANGELOG.md entry
• This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

[zrhoffman]

This PR reverts #7068, #7172, and #7175

[ocket8888]

This does indeed seem to revert the specified changes. But I don't think it's recorded anywhere: can you explain why this is necessary? Otherwise it seems like a step backwards to anyone not in the know.