fix(deps): update module github.com/equinix/equinix-sdk-go to v0.48.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/equinix/equinix-sdk-go	v0.46.0 -> v0.48.0

---

Release Notes

equinix/equinix-sdk-go (github.com/equinix/equinix-sdk-go)

v0.48.0

Compare Source

Features

• Fabric 4.19 api spec update (#​88) (a218df4)

v0.47.0

Compare Source

Features

• Update Fabric SDK to API Spec version 4.18 (#​84) (2c9e120)

Bug Fixes

• Code Generation: Updated Fabric Service Code to match latest 4.18 API Spec version (efac020)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 1 additional dependency was updated

Details:

Package	Change
github.com/stretchr/testify	v1.9.0 -> v1.10.0

[thogarty]

Fabric API Spec v4.18 produced breaking changes in equinix-sdk-go 0.47.0 that will break the Fabric Terraform Resources. We will need to make this version upgrade in a separate PR to ensure those breaks are fixed properly.

[ctreatma]

Fabric API Spec v4.18 produced breaking changes in equinix-sdk-go 0.47.0 that will break the Fabric Terraform Resources. We will need to make this version upgrade in a separate PR to ensure those breaks are fixed properly.

@thogarty is this upgrade still on your team's radar?

[thogarty]

@ctreatma , yes. You've asked at the right time because we're going to start working on the upgrade today. I'll have a PR up soon that we can link here.

[thogarty]

@ctreatma, do you want this to be included as a separate PR as in #845 , or would you rather that commit be added on top of this branch?

Repairs are ready to go though.

[ctreatma]

@thogarty no preference for this PR or a separate one; let's stick with #845 since it's already in progress