Adding build tags to each test file

[sanyamsinghal]

Describe the changes in this pull request

• introduced three tags - unit, integration, issues_integration
• every new test file added should have one of these tags
• any test file without tag will be executed with each tag workflow

Describe if there are any user-facing changes

N/A

How was this pull request tested?

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

[priyanshi-yb]

any test file wihtout tag will be executed with each tag workflow

Can you elaborate on this, I didn't get it what happens if a test file is added without tag?

[sanyamsinghal]

Can you elaborate on this, I didn't get it what happens if a test file is added without tag?

@priyanshi-yb

1. go test -v ./.. -> go test files without tag
2. go test -v ./... -tags='tag1' -> go test files with tag1 + files without tag
3. go test -v ./... -tags='tag2' -> go test files with tag2 + files without tag

[priyanshi-yb]

LGTM!