fix(keycloak-authz): make relationship field auth configurable at GraphQL field level

[craicoverflow]

Relationship fields needed to be configured with the database field name. This made it confusing to set auth rules since often the user does not know what the database column name is (it usually maps to {fieldName}Id, but this knowledge is not apparent from the schema and is hard to track.

This fixes that so it can be configured with the model field name instead.

This PR also updates the docs, which showed configuration happening from the 1:M side, whereas it should be from the M:1 side.

Before and after:

Comment: {
  relations: {
-    noteId: {
+    note: {
       roles: ['admin']
    }
  }
}

[machi1990]

Makes sense to me.

Can we add a test?

[craicoverflow]

A test exists already at https://github.com/craicoverflow/graphback/blob/keycloak-fix/packages/graphback-keycloak-authz/tests/KeycloakCrudService.test.ts#L358 .. but I think I can improve this as it can be configured to give a false positive (as it was doing already). I will work on that now.

[machi1990]

A test exists already at https://github.com/craicoverflow/graphback/blob/keycloak-fix/packages/graphback-keycloak-authz/tests/KeycloakCrudService.test.ts#L358 .. but I think I can improve this as it can be configured to give a false positive (as it was doing already). I will work on that now.

Thanks

[craicoverflow]

A test exists already at https://github.com/craicoverflow/graphback/blob/keycloak-fix/packages/graphback-keycloak-authz/tests/KeycloakCrudService.test.ts#L358 .. but I think I can improve this as it can be configured to give a false positive (as it was doing already). I will work on that now.

Actually...this test validates is correctly, no need for changes.