docs: add note to resource embedding and vertical filtering section

[taimoorzaeem]

Adds a note about resource embedding and vertical filtering sections that they are top-level operations. This resolves #4352.

[steve-chavez]

It doesn't look like this resolves #4352. The problem there is horizontal filtering and not vertical?

#4352 (comment) says that the confusion comes from this section:

Deletions also support Return Representation, Resource Embedding and Vertical Filtering.

On https://postgrest--4446.org.readthedocs.build/en/4446/references/api/tables_views.html

---

So to summarize, I believe we should:

• postgrest/docs/references/api/tables_views.rst

  Lines 601 to 604 in bccf7ac

  	Updates also support:
  	- :ref:`prefer_return`
  	- :ref:`resource_embedding`

  • Correct to - :ref:resource_embedding, with the exception of top-level filtering (<link>)

• postgrest/docs/references/api/tables_views.rst

  Line 702 in bccf7ac

  Deletions also support :ref:`prefer_return`, :ref:`resource_embedding` and :ref:`v_filter`.

  • Change here to a bullet list, same as above "Updates"
  • Correct to - :ref:resource_embedding, with the exception of top-level filtering (<link>)

[wolfgangwalther]

After reading the discussion about the breaking change again, I think we should not document this behavior. This is a bug that needs to be fixed by throwing an error accordingly.

[laurenceisla]

Can we consider it a bug if we are actively testing for it (and for a while now)?

postgrest/test/spec/Feature/Query/DeleteSpec.hs

Lines 73 to 78 in bccf7ac

	it "can embed (parent) entities" $
	request methodDelete "/tasks?id=eq.8&select=id,name,project:projects(id)" [("Prefer", "return=representation")] ""
	`shouldRespondWith` [json|[{"id":8,"name":"Code OSX","project":{"id":4}}]|]
	{ matchStatus = 200
	, matchHeaders = ["Content-Range" <:> "*/*"]
	}

Not against removing this behavior, but I think it could still be considered a breaking change due to these tests.