Adding the system table for row level security

[mamcx]

Description of Changes

NOTE: The design changes after several meetings with the team to improve the ergonomics of module compilation.

Add a new system table st_row_level_security to store the SQL queries for row-level security.

This is a first step to add support for authorization. This PR doesn't validate that the queries are valid, that will done when #1602 is implemented.

Closes #1600.

Expected complexity level and risk

2: It adds a new system table and because we haven't yet migrated support for them, it needs a recreate of the db.

Testing

• Add extra test for RLS
• Because we don't have any RLS in the initial bootstrap I also add a test for reload after creating one
• Check using the SQL cli the new table

[kazimuth]

Looks great. We've ended up with a lot of boxes to check when adding stuff to the schema, good job navigating all that. Maybe we should document the process somewhere.

You may also want to add row-level-security to crates/schema/src/auto_migrate.rs. It seems to me that arbitrary changes to row-level security can be performed automatically.

[mamcx]

It seems to me that arbitrary changes to row-level security can be performed automatically.

If we need to check the validity of the sql then probably not.

[joshua-spacetime]

My main questions are:

1. Can we get rid of the name column? I believe we can.
2. Do we need a primary key column? I believe we don't.

[mamcx]

My main questions are:

1. Can we get rid of the name column? I believe we can.
2. Do we need a primary key column? I believe we don't.

Yes, is already done