Fix collector creation error by including all fields in initial create request

[vsinghal13]

Description

Fixes a bug where hosted collector creation would show an error to the user despite the collector being successfully created.

Problem

The resourceSumologicCollectorCreate function was using a two-step process:

1. Create a minimal collector (only name and collectorType)
2. Call resourceSumologicCollectorUpdate to set remaining fields

If step 2 failed (due to ETag issues, timing problems, or API errors), the function would return an error even though the collector was already created in step 1. This led to:

• Confusing error messages for users
• Collectors existing in Sumo Logic but not in Terraform state
• Potential issues with retry attempts creating duplicate collectors

Solution

Changed resourceSumologicCollectorCreate to include all fields in the initial CreateCollector API call:

• name
• description
• category
• timezone (with default "Etc/UTC")
• fields

The function now calls resourceSumologicCollectorRead directly instead of going through resourceSumologicCollectorUpdate.

Backward Compatibility

This change is fully backward compatible:

• Optional fields use omitempty JSON tags, so empty values aren't sent to the API
• The Sumo Logic API accepts all these fields during collector creation
• Behavior is identical to the previous implementation, just without the separate update step

Check list

• Describe the changes and their purpose
• Update HTML docs (if applicable)
  • preview tool
• Update CHANGELOG.md
• Check CONTRIBUTING.md for anything forgotten

[github-actions]

⚠️ Warning: Please update CHANGELOG.md with your changes.

[rishabhkhatri09]

Let's also check if any acceptance test also needs to be updated, otherwise LGTM