UI: Implement new policy SS + modal designs

[hellobontempo]

This PR adds the ability to create an ACL or RGP policy inline when creating a group or entity. It also filters out the root policy from the dropdown.

---

Example A:

users that can list and read policies but cannot create, will only see a dropdown of existing policies

path "sys/policies*" {
    capabilities = ["read", "list"]
}
path "identity/entity/*" {
  capabilities = ["read", "update", "list", "create"]
}
path "identity/group/*" {
  capabilities = ["read", "update", "list", "create"]
}

---

Example B:

user cannot list or create policies, string list input appears

path "sys/policies*" {
    capabilities = ["read"]
}
path "identity/entity/*" {
  capabilities = ["read", "update", "list", "create"]
}
path "identity/group/*" {
  capabilities = ["read", "update", "list", "create"]
}

---

Type RGP is disabled unless the user has Sentinel (enterprise feature)

[zofskeez]

Nice work! I left some comments. It's probably out of the scope of this work but given the complexity of the SearchSelect component I'm surprised that we have somewhat duplicated it for the modal version. It would be great if we could incorporate the modal into the primary component if possible but I'm not familiar with the component and would love to learn more about it.

[hellobontempo]

Curious about feedback here. Having this object felt like a nice, concise way to document the list of different edit types and quickly reference whether or not they render a <FormFieldLabel>.

But if this feels overly complicated I can refactor to more similarly mimic the template's original conditional

[zofskeez]

Nice! I wonder if we could iterate on this in the future and export it somewhere and then consume the different types in models as well?

[hashishaw]

Wowza, great work on this! A few more things to address, although none are major. I'll play around with the branch and then approve if it looks good from there

[hashishaw]

I understand we might not need this in the modal version, but at some point we had to be able know in the parent whether the user picked a new item, so that we could show the form inline. Maybe in a future where the two components are merged, we can only show forms in a modal? 🤩

[zofskeez]

Nice work!

[zofskeez]

Nice! I wonder if we could iterate on this in the future and export it somewhere and then consume the different types in models as well?

[github-advanced-security]

Semgrep Scanner found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.

[hashishaw]

😭 it's beautiful, let's ship it

Really though, great work on this and loved the collaboration involved!