TT-10430: add integration tests for mserv and mservctl

[mitjaziv]

Description

Change adds ovh/venom integration test for mserv and mservctl.

Related Issue

TT-10430

Motivation and Context

Test Coverage For This Change

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• Make sure you are requesting to pull a topic/feature/bugfix branch (right side). If PRing from your fork, don't come from your master!
• Make sure you are making a pull request against our master branch (left side). Also, it would be best if you started your change off our latest master.
• My change requires a change to the documentation.
  • If you've changed APIs, describe what needs to be updated in the documentation.
• I have updated the documentation accordingly.
• Modules and vendor dependencies have been updated; run go mod tidy && go mod vendor in applicable directories.
• I have added tests to cover my changes.
• All new and existing tests passed.
• Check your code additions will not fail linting checks:
  • gofmt -s -w .
  • go vet ./...
  • golangci-lint run

[komuw]

For integration/bundle/bundle.zip one thing we could do is upload it as a release asset similar to

mserv/.github/workflows/release.yml

Lines 92 to 100 in 0ea7617

	- name: Attach macOS binary
	uses: actions/upload-release-asset@v1
	env:
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
	with:
	upload_url: ${{ steps.draft-release.outputs.upload_url }}
	asset_path: ./${{ env.BINARY_NAME }}.macos.amd64/${{ env.BINARY_NAME }}
	asset_name: ${{ env.BINARY_NAME }}.macos.amd64
	asset_content_type: application/octet-stream

and that way we wouldn't have to include it in git.
Though I'm not very sure if that would work well.