chore: changeset for unreleased read primitives (minor → 1.1.0)

[techiejd]

What

Adds the consolidated changeset for everything merged since 1.0.1, plus the changeset-config fix that keeps the release a minor (1.1.0) instead of a major.

changeset status confirms all four packages bump to 1.1.0:

payloadcms-vectorize          1.1.0
@payloadcms-vectorize/pg      1.1.0
@payloadcms-vectorize/cf      1.1.0
@payloadcms-vectorize/mongodb 1.1.0

Why one changeset

Per the plan to ship one minor changeset covering the stacked PRs rather than one per PR. The unreleased, changeset-less PRs since 1.0.1 are:

• feat: findByIds read primitive #62 findByIds read primitive (feat)
• fix(mongodb): return all stored fields from search for CF/PG parity (+ README parity) #63 mongodb: return all stored fields from search() — CF/PG parity (fix)
• feat: add searchByEmbedding method #68 searchByEmbedding Local API method (feat)
• feat: add populateEmbedding option to search and searchByEmbedding #70 populateEmbedding on search() / searchByEmbedding() + embedding typed on VectorSearchResult / EmbeddingRecord (feat)

(#61 cf workers-types refactor and #67/#69 docs are internal/non-user-facing and intentionally omitted from the changeset — say the word if you want #61 noted.)

Config change

.changeset/config.json gains ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.onlyUpdatePeerDependentsWhenOutOfRange: true. Without it, the four-package fixed group's peer-dependency cascade turns this minor into a 2.0.0 major. With it, changeset status resolves to 1.1.0 (verified).

No code changes — changeset + config only.