chore: expose webhook url when creating webhook triggers

[rssnyder]

expose webhook url when creating webhook triggers [Feature]

Today when creating webhook triggers we do not return from the create call the actual webhook that is created. The webhook URL is the most valuable piece of data a user needs when creating a webhook trigger.

By adding this to the response payload we will be able to extract and use it in the Terraform provider.

DEPENDS ON harness/harness-go-sdk#685

Summary:
If I create a webhook trigger, I'm not able to actually use the webhook that is created

Details:
Simply expose the data from the response

Related Issues:
harness/harness-go-sdk#685

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.

I have used the local version of the SDK and done the dev overrides for the Terraform provider.
I created both webhook and non-webhook triggers and I can successfully create them and use data resources as well to resolve the information necessary.

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

[rssnyder]

trigger build

[rssnyder]

trigger build

[rssnyder]

@ritek01 i updated to the lasted SDK and builds are passing now