Fix windows build failure due to incompatibility between newer flutter and older google font version

[Aman071106]

PR Description

Fixes a crash on desktop startup for users on newer Flutter versions (v3.25+ / Master channel) caused by the removal of AssetManifest.json.

The google_fonts package (v6.2.1) relied on AssetManifest.json.
Newer Flutter builds generate AssetManifest.bin instead.
This PR upgrades google_fonts to ^6.3.3, which includes support for the binary manifest.

Changes

• Upgraded google_fonts from ^6.2.1 to ^6.3.3 in packages/apidash_design_system/pubspec.yaml.

Related Issues

• Closes Desktop crash: Unable to load asset: "AssetManifest.json" on startup #972

Checklist

• I have gone through the contributing guide
• I have updated my branch and synced it with the project main branch before making this PR
• I am using the latest Flutter stable branch
• I have verified the fix manually (Regression verified on Stable; Fix verified via Changelog for Master)

Added/updated tests?

• No, and this is why: Dependency update only.

OS on which you have developed and tested the feature?

• Windows

[ShashwatXD]

@Aman071106 you shoudn't push the pubspec.lock file.

[Aman071106]

@ShashwatXD app uses a pubspec.lock and changes in it are allowed so that all can have same dependency configuration across all environments. You shouldn't push a pubspec.lock while making dart packages. If you have a explanation, provide why it is irrelevant to push a pubspec.lock.

[ShashwatXD]

@Aman071106 .lock files are auto-generated via flutter pub get from the .yaml file, since they can be regenerated, they usually don’t need to be committed.