Build Retention should be revisited

The staging pipeline failed to retain a build of a product repo in the `Enable permanent build retention` step and to unblock the pipeline we set `continueOnError` to true after determining that the issue is not blocking
We should revisit this fix and consider
- distinguishing between a build found exception as opposed to api error
- changing the `ErrorActionPreference` in the script
- figuring out how to determine if a failure in this stage is blocking - does it depend on the specific build that's missing? and documenting it for the release team

Teams thread: https://teams.microsoft.com/l/message/19:96cdb5beef6840178d85bc2c22028226@thread.skype/1684152497666?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=147df318-61de-4f04-8f7b-ecd328c256bb&parentMessageId=1684152497666&teamName=.NET%20Eng%20Services&channelName=V-Team%20-%20Release%20Infrastructure&createdTime=1684152497666

Start with the staging pipeline's `Enable permanent build retention` step and the script currently using `continueOnError`. Review how the script handles `ErrorActionPreference` and separates a missing build from an API error. Done means determining which failures block release, updating the retention handling, and documenting the rule for the release team.

Written by the indexing model from the issue text.