[auth] Update Condition Attribute enum values

[bcmdarroch]

🔩 Description: What code changed, and why?

The allowed values for a rule's Condition Attribute were a mix of plural and singular and didn't match how they're meant to be shown in the UI. Now they've been updated to match this list provided by superteam:

*Node Attributes*
Chef Organization
Chef Server
Environment
Chef Role
Chef Tag
Chef Policy Name
Chef Policy Group

*Event Attributes*
Chef Organization
Chef Server

👟 How to Build and Test the Change

curl -kH "api-token: $TOK" https://localhost/apis/iam/v2beta/projects -d "$(jq -n '{ id: "bar", name: "my bar project"}')" | jq .

# no longer works
curl -kH "api-token: $TOK" https://localhost/apis/iam/v2beta/projects/bar/rules -d "$(jq -n '{ id: "rule2", name: "my foo rule", type: "NODE", conditions: [{ operator: "EQUALS", attribute: "CHEF_ORGS", values: ["The Misfits"]}]}')" | jq .

# works
curl -kH "api-token: $TOK" https://localhost/apis/iam/v2beta/projects/bar/rules -d "$(jq -n '{ id: "rule2", name: "my foo rule", type: "NODE", conditions: [{ operator: "EQUALS", attribute: "CHEF_ORGANIZATION", values: ["The Misfits"]}]}')" | jq .

✅ Checklist

• Tests added/updated?
• Docs added/updated?

📷 Screenshots, if applicable

[blakestier]

:hrm: Are there any user-facing docs we'd need to update? Or concerns about backwards compatibility?

[susanev]

these maybe?
https://automate.chef.io/docs/client-runs/#node-filters
https://automate.chef.io/docs/reports/#search-bar-and-filters

[afiune]

❤️ Love to see this kind of cleanup in the code! 💯

[afiune]

(nothing to do with this PR just a question to myself and @lancewf)

Do we need this foundMatch logic? why not just return true in like 121 like the other functions? (I might be missing something)

[msorens]

LGTM!