Store Apache Traffic Server and grove logs in /var/log/trafficserver

[zrhoffman]

This PR changes configuration to log Apache Traffic Server and Grove to /var/log/trafficserver instead of /opt/trafficserver/var/log/trafficserver so that the logs are on a different partition than the application itself.

---

Which Traffic Control components are affected by this PR?

• Traffic Control Cache Config (t3c, formerly ORT) - tests
• Apache Traffic Server
• Grove
• Transitive Source Build targeting ATS
• Automation - Ansible roles configuration for grove log directory

What is the best way to verify this PR?

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

PR submission checklist

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

[ntheanh201]

Should we also upgrade ATS's version? https://github.com/apache/trafficcontrol/pull/7958

[zrhoffman]

Should we also upgrade ATS's version? #7958

Definitely. I think the only reason that #7958 is not approved already is the realpath on macOS issue that the reviewer encounted. Hopefully #7981 will unblock that.

[ntheanh201]

I cannot test DS with your new ATS Edge, when I try to start ATS service, it shows that you still have to change to /var/log/trafficserver with traffic.out

P/s: I created a PR to your repo to fix this issue, can you take a look? @zrhoffman

[zrhoffman]

I cannot test DS with your new ATS Edge, when I try to start ATS service, it shows that you still have to change to /var/log/trafficserver with traffic.out

P/s: I created a PR to your repo to fix this issue, can you take a look? @zrhoffman

Thanks @ntheanh201! zrhoffman/trafficcontrol#122 is merged.

[ntheanh201]

Is there anything else in this PR that you need to check? the CI failed? @zrhoffman