Resolve group_path to full_path when creating compliance frameworks

What does this MR do and why?

Fixes an issue where trying to create a compliance framework on a group named "a" would resolve to the wrong group with the same ending.

Two groups: "a" and "c/b/a". If the second group was created first and the group_path was input as "a", the second group would be returned.

This fixes it and requires resolves only to an exactly matching full path.

How to set up and validate locally

• Create a subgroup called hello/max
• Create a root group called max
• Make sure you're an owner of max. (The root group)
• Create a compliance framework using the externalAuditEventDestinationCreate GraphQL mutation. Use max as the groupPath parameter.
• Ensure that the framework was created correctly, and on the correct group.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.