Error creating a release with artifact references

[davewalter]

Describe the bug

We have started seeing errors when attempting to create new releases for a product that includes a number of artifact references:

2023/04/11 01:25:10.688403 PivNet Resource version: 3.0.2
2023/04/11 01:25:12.222560 Validating EULA: 'eula'
2023/04/11 01:25:13.802291 Validating release type: 'release type'
2023/04/11 01:25:14.536227 Creating new release with config: {ProductSlug:product-slug Version:1.2.3 ReleaseType:release type ReleaseDate: EULASlug:eula Description: ReleaseNotesURL: Controlled:false ECCN:eccn LicenseException:none EndOfSupportDate: EndOfGuidanceDate: EndOfAvailabilityDate: CopyMetadata:false}
2023/04/11 01:25:14.536271 No release date found - using default release date - [map[release date:2023-04-11]]
2023/04/11 01:25:15.900819 Created new release with ID: 1234567
2023/04/11 01:25:15.900896 file glob not provided - skipping upload to s3
ERROR: Get https://network.tanzu.vmware.com/api/v2/products/product-slug/artifact_references: EOF

Reproduction steps

1. Set up a product with a large number of artifact references.
2. Attempt to create a new release.

Expected behavior

We should be able to create a new release of the product.

Additional context

Each release of our product includes 8 artifact (image) references. We estimate that we have roughly 2000 artifact references associated with the product across all releases. The GET /api/v2/products/:product_slug/artifact_references API endpoint attempts to retrieve all artifact references for the given product slug, which times out when we run it manually.