Step in Github action workflow to verify each go test files have a build tag assigned to it

[sanyamsinghal]

Describe the changes in this pull request

Output in case of go build tag missing in test files

Describe if there are any user-facing changes

NA

How was this pull request tested?

Existing tests

Does your PR have changes that can cause upgrade issues?

Component	Breaking changes?
MetaDB	Yes/No
Name registry json	Yes/No
Data File Descriptor Json	Yes/No
Export Snapshot Status Json	Yes/No
Import Data State	Yes/No
Export Status Json	Yes/No
Data .sql files of tables	Yes/No
Export and import data queue	Yes/No
Schema Dump	Yes/No
AssessmentDB	Yes/No
Sizing DB	Yes/No
Migration Assessment Report Json	Yes/No
Callhome Json	Yes/No
YugabyteD Tables	Yes/No
TargetDB Metadata Tables	Yes/No

[makalaaneesh]

with the way that our pipelines are at the moment, if there are no tags on a test file, will they not run?

[sanyamsinghal]

@makalaaneesh it will run.
there are two cases for test file:

1. with tag
2. without tag

go test -v ./... -tags tag1 executes the test with tag1 and untagged
go test -v ./... -tags tag2 executes the test with tag2 and untagged

so the untagged ones will be unnecessarily executed.
Anyways since we are using tags now, so each file should be categorised to a tag.