Added unique resource IDs per owner

[aaguiarz]

In the current decision*.json files, the same todo ID is used when checking if users can_update_todo when a specific user is the owner. This implies that the same Todo item is owned by different users, which is probably not intended.

{
      "request": {
        "subject": {
          "type": "user",
          "id": "CiRmZDQ2MTRkMy1jMzlhLTQ3ODEtYjdiZC04Yjk2ZjVhNTEwMGQSBWxvY2Fs"
        },
        "action": {
          "name": "can_update_todo"
        },
        "resource": {
          "type": "todo",
          "id": "7240d0db-8ff0-41ec-98b2-34a096273b9f",
          "properties": {
            "ownerID": "[email protected]"
          }
        }
      },
      "expected": false
    },

This PR updates the decision*.json files to use unique todo:id identifiers for todo items owned by different users:

• [email protected] - 7240d0db-8ff0-41ec-98b2-34a096273b91
• [email protected] - 7240d0db-8ff0-41ec-98b2-34a096273b92
• [email protected] - 7240d0db-8ff0-41ec-98b2-34a096273b93
• [email protected] - 7240d0db-8ff0-41ec-98b2-34a096273b94
• [email protected] - 7240d0db-8ff0-41ec-98b2-34a096273b95

In addition of making it more correct, it simplifies the implementation in ReBAC systems, as they can store the { user:x, owner, todo:y } relation in the database instead of obtaining it from the context.

[netlify]

👷 Deploy request for authzen-todo pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	8b9ea0b

[ogazitt]

tested against a few of the implementations, they all pass