test(e2e): Update test to mitigate timing flake

[moduli]

This PR attempts to address a flaky failure on an e2e test

 === RUN   TestCliTcpTargetWorkerConnectTarget
    scope.go:85: Created Org Id: o_ZxSfdYzY8A
    scope.go:127: Created Project Id: p_b0mudNwKQ2
    target_tcp_worker_connect_ssh_test.go:77: Created Vault Credential
    target_tcp_worker_connect_ssh_test.go:97: Created Vault Cred Store Token
    credential.go:99: Created Credential Store: csvlt_ocCer9Zv2D
    credential.go:166: Created Credential Library: clvlt_RT0eBgJjeq
    target.go:127: Created Target: ttcp_njQTKJneDC
    target_tcp_worker_connect_ssh_test.go:156: Successfully connected to target
    target_tcp_worker_connect_ssh_test.go:180: Successfully failed to connect to target with wrong worker filter
    target_tcp_worker_connect_ssh_test.go:208: Adding API tag to worker...
    target_tcp_worker_connect_ssh_test.go:250: Successfully connected to target with new filter
    target_tcp_worker_connect_ssh_test.go:284: Successfully failed to connect to target with wrong filter
    target_tcp_worker_connect_ssh_test.go:287: Changing API tag on worker...
    target_tcp_worker_connect_ssh_test.go:307: 
        	Error Trace:	/src/boundary/testing/internal/e2e/tests/base_with_worker/target_tcp_worker_connect_ssh_test.go:307
        	Error:      	Received unexpected error:
        	            	exit status 255
        	Test:       	TestCliTcpTargetWorkerConnectTarget
        	Messages:   	kex_exchange_identification: read: Connection reset by peer
        	            	Connection reset by 127.0.0.1 port 33913

It looks like we observed one instance where this test failed to connect to a target after changing and API tag on a worker. I have only seen this fail once, which seems to indicate it's some timing thing. For now, this PR adds some retries when connecting to the target after changing worker tag properties.

https://hashicorp.atlassian.net/browse/ICU-15923