Problem with permission for a table located in another scheme not public
I'm using the latest version of dockerized Postgraphile on Manjaro Linux with Kernel 5.16.14-1-MANJARO.

Next, I have two schemes on my db: **schemeA** (private) and **schemeB** (public). Evidently **schemeB** is exposed by Postgraphile only.

I have a table (**schemeA**) with this definition:

```
CREATE TABLE schemeA.my_table (
  id SERIAL PRIMARY KEY,
  field1 TEXT
);

ALTER TABLE schemeA.my_table ENABLE ROW LEVEL SECURITY;

CREATE POLICY logged_users ON schemeA.my_table TO authorized_group
  USING (id = current_setting('jwt.claims.id', true)::uuid);
```

And I have this function (**schemeB**):

```
CREATE OR REPLACE FUNCTION schemeB.create_something(IN data text, OUT _result INTEGER) 
AS $$
BEGIN
  INSERT INTO schemeA.my_table (field1) VALUES (data) RETURNING id INTO _result;
  RETURN;
END;
$$ LANGUAGE plpgsql STRICT SET search_path = schemeB, pg_temp;

GRANT EXECUTE ON FUNCTION schemeB.create_something(text) TO authorized_group;
GRANT INSERT (field1) ON schemeA.my_table TO authorized_group;
```

When trying run this mutation in Postgraphile:

```
mutation MyMutation {
  createSomething(input: {data: "chesu"}) {
    _result
  }
}
```

I got a error message with a text like this **permission denied for table *my_table***.

My workaround is to use this sentence for my function:
```
$$ LANGUAGE plpgsql STRICT SECURITY DEFINER SET search_path = schemeB, pg_temp;
```
I know this is not recommended, so what am I missing?
