BillingBudgetsBudget permadiff due to suspected mismatch in array order

[justinsb]

Issue Summary:
A user has reported that when trying to configure a BillingBudgetsBudget resource with the budgetFilter.projects field, KCC is throwing a permadiff error. This appears to be caused by a mismatched ordering of the projects list between the local configuration and the API. This can lead to the creation of duplicate resources.

Error:

"error": "diffs exist after apply: [Field BudgetFilter.Projects[0]: got \"projects/project1\", want \"projects/project2\" Field BudgetFilter.Projects[1]: got \"projects/project2\", want \"projects/project3\" Field BudgetFilter.Projects[3]: got \"projects/project3\", want \"projects/project1\"]",

Reproduction Steps:

1. Create a BillingBudgetsBudget resource with the budgetFilter.projects field defined with a list of projects.
2. Apply the KCC resource.
3. Observe the permadiff and potential for duplicate resource creation.

Environment:
Config Connector Version: 1.131.0