Add separate profiles for Varnish cache

[AbdelrahmanElawady]

Create separate profiles for Varnish cache so users won't need to change cache profiles manually.

Closes: #7721

---

Which Traffic Control components are affected by this PR?

• CDN in a Box

What is the best way to verify this PR?

Run CIAB with Varnish and check Traffic Portal that the right profile is associated with both Varnish and ATS:

• Change Dockerfile in edge server to point to varnish/Dockerfile instead of cache/Dockerfile
• Change edge status to ONLINE (until TM integration is done).
• Run CIAB and expose ports with docker-compose -f docker-compose.yml -f docker-compose.expose-ports.yml up --build
• Open Traffic Portal and check profile associated with each cache server.

Note: this applies to Mid-01 and Mid-02 too. The only issue is if running all servers with ONLINE status.

Note: new profiles is the same as ATS ones with description, name and parameters that cause issues (chkconfig and package) changed. easiest way to check is to run diff for ATS and Varnish profiles,

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)