Ensure all the required fields are populated in the html report for new flattened issues approach

[sanyamsinghal]

Describe the changes in this pull request

This PR includes:

• Having relevant value based on Issue field
• Populating Description and Name in all query issues
• Replacing AnalyzeSchemaIssue.Reason field to be equivalent QueryIssue.Description instead of QueryIssue.Name field
• QueryIssue.Description will only contain dynamic information, rest all fields mostly will be static.
• Fixed all the automation tests based on the new strings(reason/description etc)

Describe if there are any user-facing changes

nothing as such, only text has changed for some of the issue fields (reported in assess and analyze)

How was this pull request tested?

Fixing Existing tests to pass.

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

[sanyamsinghal]

Jenkins Pipelines

1. Running assessment related tests - https://jenkins.dev.yugabyte.com/job/users/job/yb-voyager-testing/job/yb-voyager-testing-pipeline/4477/