Technical writer review of Geo framework documentation

Recently I merged !35154 (merged). It contained small documentation changes for the SSF. But it did not get approval from a TW. I merged it because I had an MR in flight and wanted to iterate fast on it.

But @marcel.amirault made a very good point: (+2 comments)

@toon @vsizov Don't forget to get a TW to do the final review and merge, in this case @marcia is the person responsible for development documentation, or @mjang1 for Geo docs: https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments-to-other-projects-and-subjects 🙏

I think we might have a couple more of these MRs, with minimal changes on the doc, but don't really want to bother a TW for every small changes (most changes will be in the code snippets anyway).

So I suggest we skip TW reviews on doc/development/geo/framework.md for a while, and schedule a thorough review of the doc again when the document is more stable.