fix: enable selinux for docker

[sweatybridge]

What kind of change does this PR introduce?

Bug fix, feature, docs update, ...

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

[github-actions[bot]]

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Validation Output

Success! The configuration is valid.

Terraform Plan 📖success

Show Plan

terraform
data.supabase_branch.all: Reading...
data.supabase_pooler.production: Reading...
data.supabase_branch.all: Read complete after 1s
data.supabase_pooler.production: Read complete after 2s

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # supabase_settings.production will be created
  + resource "supabase_settings" "production" {
      + api         = jsonencode(
            {
              + db_extra_search_path = "public,extensions"
              + db_schema            = "public,storage,graphql_public"
              + max_rows             = 1000
            }
        )
      + id          = (known after apply)
      + project_ref = "jgcajpecsmkatlbzsstn"
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Changes to Outputs:
  + pooler_url      = "postgresql://postgres.jgcajpecsmkatlbzsstn:[YOUR-PASSWORD]@aws-0-ap-southeast-1.pooler.supabase.com:6543/postgres"

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.

Pusher: @sweatybridge, Action: pull_request, Working Directory: supabase/remotes, Workflow: CI