fix: [PL-63285]: Usergroup v2 update

[abhishekdas06]

Title: [Component/Feature] Short Description of the Change

Summary:
Provide a brief overview of what the PR does and why it is needed.

Details:
Explain the changes in detail, including any relevant context or background information.

Related Issues:
Reference any related issues or tickets

Testing Instructions:
Describe how the changes were tested. Include any test cases or steps to verify the functionality.
Please include the below test scenario with your changes.

• Create the resource and execute terraform apply. (Verify the resource is created)
• Execute terraform apply again without any changes. (Verify no changes should be done)
• Update the resource and execute terraform apply. (Verify the resource updated successfully)
• Remove the content from resource file and execute terraform apply. (Verify the resource has been deleted)
• Add again the resource and execute the terraform apply. (Verify the resource is created)
• Verify the import the resource file is working fine.
• In case of remote entity, Verify for both default and non default branch.

#Testing

Imported resource with user_emails

Terrafrom plan mentions 0 changes

Without any user_email or users field

State file shows only user_emails and users is null which is expected

With users field

Terraform import doesn't have access to user_emails field or users field while importing hence it will always import using users_email.
In case userGroupV2 API is not present in customers environment then we fallback to V1 API behaviour

Terraform plan

For already created resources, we only see the diff based on the fields which have been provided.
During plan we have the information of whether user_email or users is present

Screenshots:
Include before and after screenshots to visually demonstrate the changes.
Checklist:

• Code changes are well-documented.
• Tests have been added/updated.
• Changes have been tested locally.
• Documentation has been updated.

PR Check triggers

• Build: trigger build
• Sub Category Field Check: trigger subcategoryfieldcheck
• gitleaks: trigger gitleaks

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ ritek01
❌ abhishekdas06
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ritek01]

LGTM ✅