fix: unknow type in sync

[CurryYangxx]

Background

This is a fix for sync between different versions(The new version includes new DB model types to sync).
When testing the new Socket.io feature, if we push the new commit that includes the socket.io request. Then we use an older version and pull, there are some unexpected behaviors

• git sync
  • Will recognize socket.io as websocket and can not select it.
• cloud sync
  • Can not pull an unsynced workspace or new commit (Unknown database type causes js error)

This pr can fix the 2 issues above, but when we check the diff in the older version, the new type request was deleted.
Consider whether this can be fixed or the user can be better prompted

[Copilot]

Pull Request Overview

This PR addresses sync issues when handling unknown model types between different versions. Key changes include:

• Adding a type check before upserting documents in the backend project sync logic.
• Enhancing the meta schema in the v5 import parser to ensure websocket request IDs follow the expected pattern.
• Logging a warning and gracefully handling cases when a database collection is missing.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
packages/insomnia/src/sync/vcs/pull-backend-project.ts	Introduces a type guard on document upserts to prevent syncing issues.
packages/insomnia/src/common/import-v5-parser.ts	Adds a schema validation to ensure websocket request IDs start with "ws-req".
packages/insomnia/src/common/database.ts	Logs a warning and returns an empty result when the database collection is missing.

Comments suppressed due to low confidence (1)

packages/insomnia/src/sync/vcs/pull-backend-project.ts:60

• [nitpick] Consider renaming 'allModelType' to 'allModelTypes' to more clearly indicate that it represents a collection of model types.

const allModelType = models.types();