limited update/delete requires explicit order

* limited update/delete now works on views with explicit order
* no default order, enforce order presence
* apply row count to ensure limited mutations
* move requiring order to ApiRequest

test/spec/fixtures/schema.sql

@@ -2493,6 +2493,12 @@ create table limited_update_items_no_pk(
 create view limited_update_items_view as
 select * from limited_update_items;
 
+create view limited_update_items_wnonuniq_view as
+select *, 'static'::text as static from limited_update_items;
+
+create view limited_update_items_cpk_view as
+select * from limited_update_items_cpk;
+
 create table limited_delete_items(
   id int primary key
 , name text
@@ -2512,6 +2518,12 @@ create table limited_delete_items_no_pk(
 create view limited_delete_items_view as
 select * from limited_delete_items;
 
+create view limited_delete_items_wnonuniq_view as
+select *, 'static'::text as static from limited_delete_items;
+
+create view limited_delete_items_cpk_view as
+select * from limited_delete_items_cpk;
+
 create function reset_limited_items(tbl_name text default '') returns void as $_$ begin
   execute format(
   $$