Remove @meshery/schemas from peerDependencies

[saurabhraghuvanshii]

Notes for Reviewers

This PR fixes #

Signed commits

• Yes, I signed my commits.

[leecalcote]

How does this impact dependent projects?

[saurabhraghuvanshii]

This change is backwards compatible and does not break existing dependents.

• Projects that already depend on @meshery/schemas (e.g. Meshery UI): No change in behavior. When they upgrade to the new sistent version, npm will install @meshery/schemas as a transitive dependency and will dedupe when the version range is satisfied, so they typically keep using the same copy they already have.
• Projects that do not list @meshery/schemas (e.g. layer5 site): They currently have to add it manually to fix the build. With the new sistent, it is brought in automatically, so their builds work without that extra step.

Dependent projects are not negatively impacted; they either keep working as before or start working without having to add the peer dependency themselves.

[Bhumikagarggg]

@saurabhraghuvanshii Thank you for your contribution! Let's discuss this during the website call tomorrow at 6:30 PM IST | 7 AM CST Add it as an agenda item to the meeting minutes, if you would 🙂