bump cf-tcp-router

[winkingturtle-vmw]

Follow up for #334

bump gorouter
bump multierror
bump route-registrar
bump routing-api
bump routing-api-cli
bump routing-info

Submodule src/code.cloudfoundry.org/cf-tcp-router 004af19..89625e5:

Use bin/test.bash for running tests (#15)
Submodule src/code.cloudfoundry.org/gorouter 31a88e6..587fdbd:
Use bin/test.bash for running tests (#357)
Submodule src/code.cloudfoundry.org/multierror 0623381..add4c8e:
Merge pull request #6 from cloudfoundry/with-bin/test.bash
Submodule src/code.cloudfoundry.org/route-registrar 247293e..958da78:
Use bin/test.bash for running tests (#35)
Submodule src/code.cloudfoundry.org/routing-api dd977026..84d22269:
Use bin/test.bash for running tests (#35)
Submodule src/code.cloudfoundry.org/routing-api-cli 045f777..5c9811f:
Use bin/test.bash for running tests (#16)
Submodule src/code.cloudfoundry.org/routing-info 079a2734..3a6d4ccb:
Use bin/test.bash for running tests (#5)

---

What is this change about?

In your own words, describe this proposed change and the problem it solves. If GitHub has prepopulated any text above here with info from your commit message, please clean it up and account for it in this section.

What type of change is this?

• [Breaking Change]: the change removes a feature or introduces a behavior change to core functionality (request routing, request logging)
• [Minor Feature/Improvement]: the change introduces a new feature or improvement that doesn't alter core behavior
• [Bug Fix]: the change addresses a defect

If you have selected multiple of the above, it may be wise to consider splitting this PR into multiple PRs to decrease the time for minor changes + bugs to be resolved.

Backwards Compatibility

If this is a breaking change, or modifies currently expected behaviors of core functionality (request routing or request logging), how has the change been mitigated to be backwards compatible?

Should this feature be considered experimental for a period of time, and allow operators to opt-in? Should this apply immediately to all routing-release deployments?

How should this be tested?

Are there any non-automated tests that should be performed against this change for validation? Please provide steps, and expected results for before + after the change.

Additional Context

Please provide any additional links or context (issues, other PRs, Slack discussions) to help understand this change.

PR Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have made this pull request to the develop branch.
• I have run all the unit tests.
• I have given thought to the backward-compatibility requirements of this change, and listed any mitigations above.
• (Optional) I have run Routing Acceptance Tests and Routing Smoke Tests.
• (Optional) I have run CF Acceptance Tests.