Resource rename and delete

[byewokko]

Closes #99
Closes #100

Introduce endpoints for renaming and deleting resources.

Known limitations: Deleted resources may still be present in existing sessions and ID tokens.

Soft-delete (suspend) resource

Resource is marked as deleted, but stays in the database. It is also unassigned from all roles.

DELETE /resource/<resource_name>

Undelete resource

Same endpoint as creating a new resource.

POST /resource/<resource_name>
{}

Hard-delete resource

Resource is actually deleted from the database. It is also unassigned from all roles.

DELETE /resource/<resource_name>?hard_delete=true

Rename resource

A shorthand for creating a new resource and deleting the old one.

PUT /resource/<old_resource_name>
{
  "name": "<new_resource_name>"
}

List roles with a specific resource

Tenant roles + global roles

GET /role/<tenant>?resource=<resource_name>

All roles (superuser only)

GET /role?resource=<resource_name>

Other changes

• Soft-deleted resources are excluded from the resource list (GET /resource) by default. Add query parameter include_deleted=true to include them.