Chore: Fix type generation script

[aniketkatkar97]

I worked on refactoring the json2ts script to:

1. Fix the issue with current type generation script where we only generated types for the changed schemas resulting in the types of other schemas falling behind.
   Ex.:
   If schema1.json has ref inside referring to schema2.json, according to the existing script, making some change in the schema2.json regenerated type schema2.ts but since it might have affected schema1.json as well, we were not updating schema1.ts. The updated script will now generate the types for all the schemas.
2. Improved the speed for time generation, taking too much time in pre-commit. The type generation should not take more than 1.5 mins (as compared to previous time of around 4-5mins)
3. Fixed the generated types according to the existing schemas.

Type of change:

• Bug fix
• Improvement
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

[github-actions]

Jest test Coverage

UI tests summary

Lines	Statements	Branches	Functions
	63.49% (42244/66539)	38.2% (16462/43093)	42.92% (5047/11760)

[sonarqubecloud]

Quality Gate passed for 'open-metadata-ui'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed for 'open-metadata-ingestion'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud