VTAdmin: Support for Materialize Create

[beingnoble03]

Description

This PR adds support to create a Materialize workflow directly from VTAdmin. Contains both API and Web changes.

Related Issue(s)

• VTAdmin: Enhance VReplication functionality in vtadmin UI #11690

Screenshots

Checklist

• "Backport to:" labels have been added if this change should be back-ported to release branches
• If this change is to be back-ported to previous releases, a justification is included in the PR description
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on CI?
• Documentation was added or is not required

Deployment Notes

[vitess-bot]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

• Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

• Apply the release notes (needs details) label if users need to know about this change.
• New features should be documented.
• There should be some code comments as to why things are implemented the way they are.
• There should be a comment at the top of each new or modified test to explain what the test does.

New flags

• Is this flag really necessary?
• Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

• Each item in Jobs should be named in order to mark it as required.
• If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• RPC changes should be compatible with vitess-operator
• If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
• vtctl command output order should be stable and awk-able.

[codecov]

Codecov Report

Attention: Patch coverage is 1.53846% with 64 lines in your changes missing coverage. Please review.

Project coverage is 69.38%. Comparing base (f0062e6) to head (33e74ee).
Report is 6 commits behind head on main.

Files with missing lines	Patch %	Lines
.../vtctldclient/command/vreplication/common/utils.go	0.00%	25 Missing ⚠️
go/vt/vtadmin/api.go	5.00%	19 Missing ⚠️
go/vt/vtadmin/http/workflows.go	0.00%	17 Missing ⚠️
...dclient/command/vreplication/materialize/create.go	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16941      +/-   ##
==========================================
- Coverage   69.41%   69.38%   -0.04%     
==========================================
  Files        1570     1570              
  Lines      203948   203989      +41     
==========================================
- Hits       141576   141543      -33     
- Misses      62372    62446      +74     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[arthurschreiber]

This looks great! ❤️

[mattlord]

Looks good in my testing! Would be nice to incorporate cancel/delete here if possible: #16816

Can be done in a later follow-up though.