Replaced Issue Type in html assessment report with Issue Name field

[sanyamsinghal]

Describe the changes in this pull request

• in analyze issues wherever issue name is not present assuming issue type
• using the term Issue in html report instead of Name or Type

TODO(Question): In html report, we can have a logic which check if issue.Name == "" then use issue.Type is used, since that should ideally be present for all reported issues.

Describe if there are any user-facing changes

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

[CLAassistant]

All committers have signed the CLA.

[sanyamsinghal]

https://jenkins.dev.yugabyte.com/job/users/job/yb-voyager-testing/job/yb-voyager-testing-pipeline/4652/