Refactor issue, queryissue pkgs

[makalaaneesh]

Describe the changes in this pull request

Some more refactoring on top of comments from #1873

• Move issue definitions from issue pkg into queryissue pkg
• Move IssueInstance from issue pkg into queryIssue pkg.
• Rename IssueInstance to queryIssue
• Put queryissue and queryparser under a common folder query

Describe if there are any user-facing changes

N/A

How was this pull request tested?

N/A. Existing tests suffice.

Does your PR have changes that can cause upgrade issues?

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

[priyanshi-yb]

Do we need the prefix query in the directory names of queryissue, queryparser ?

[makalaaneesh]

the query directory is just better file organization, it does not translate to any form of nesting of packages. If there was indeed some form of nesting, I agree; it would make sense to remove the "query" prefix. But since these are top-level packages, I wanted to stick to the pattern of keeping the folder name same as the package name.

[priyanshi-yb]

LGTM