SUMO-266317: Fix selectionType handling for Role V2 to avoid MatchError

[AbhishekSumo]

Issue

• The Sumo Logic Roles V2 API omits selectionType for default roles.
• In the provider Read function:
  • When the API omits the field, json.Unmarshal assigns the Go zero value ("") to SelectionType.
  • The provider calls d.Set("selection_type", roleV2.SelectionType) with that empty string.
  • The Terraform SDK interprets empty string for an optional TypeString as unset and stores null in state.
• On the next terraform apply:
  • d.Get("selection_type") returns "" (SDK converts null → "").
  • The provider sends "" to the backend.
  • The backend’s selectionTypeToAvroSelectionType throws a scala.MatchError for empty string.

Root Cause

• omitempty only affects JSON encoding, not decoding.
• When the API omits selectionType, Go’s json.Unmarshal sets it to the zero value "".
• Terraform interprets "" as unset for optional attributes and stores null.
• On update, the provider sends "" to the API instead of a valid value.

Fix

1. Normalize in Read:

• When SelectionType == "", default it to "All" before d.Set.
• Prevents Terraform from storing null and avoids perpetual diffs.

2. Force valid value in Update:

• Before calling the API, if SelectionType == "", set it to "All".
• Ensures a valid value is always sent and avoids MatchError.

[github-actions]

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

[ssharma-sumologic]

LGTM

[atishya-22]

Can we add test for this in resource_sumologic_role_v2_test.go

[github-actions]

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

[github-actions]

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

[github-actions]

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