Dont start Riak in TP/TO GHA

[shamrickus]

This PR fixes #5946 and #5947

---

Which Traffic Control components are affected by this PR?

• Automation (GHA)

What is the best way to verify this PR?

Inspect the logs and make sure traffic vault is not running. For TP, look at the artifacts and ensure that tv.log does not exist.

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]

No longer provides a Riak server

trafficcontrol/.github/actions/to-integration-tests/README.md

Line 23 in 6790479

- Provides a Riak server at address `trafficvault.infra.ciab.test`

There is no longer a Riak server

trafficcontrol/.github/actions/tp-integration-tests/README.md

Line 23 in 6790479

- provides a riak server at address `trafficvault.infra.ciab.test`

Is inserting a RIAK server still necessary?

trafficcontrol/.github/actions/tp-integration-tests/entrypoint.sh

Lines 90 to 103 in 6790479

	WITH TYPE AS (SELECT id FROM type WHERE name = 'RIAK'),
	PROFILE AS (SELECT id FROM profile WHERE name = 'RIAK_ALL'),
	STATUS AS (SELECT id FROM status WHERE name = 'ONLINE'),
	PHYS AS (SELECT id FROM phys_location WHERE name = '${PHYS}'),
	CDN AS (SELECT id FROM cdn WHERE name = '${CDN}'),
	CG AS (SELECT id from cachegroup WHERE name = '${CG}')
	INSERT INTO server(host_name, domain_name, cachegroup, type, status, profile, phys_location, cdn_id)
	SELECT 'trafficvault', 'infra.ciab.test', CG.ID, TYPE.id, STATUS.id, PROFILE.id, PHYS.id, CDN.id
	FROM TYPE
	JOIN STATUS ON 1=1
	JOIN PROFILE ON 1=1
	JOIN PHYS ON 1=1
	JOIN CDN ON 1=1
	JOIN CG ON 1=1;

No need to gitignore riak.conf

trafficcontrol/.github/actions/to-integration-tests/.gitignore

Line 24 in 6790479

riak.conf

[ocket8888]

Somehow didn't see the existing reviewer. The two things I pointed out weren't real, so I'm bowing out now.

[zrhoffman]

Looks good! Verified that Traffic Vault is not running, and, for TP, no traffic_vault.log file exists in the artifact on failure.