fix: replace builds with ids in config

[gaius-qi]

Description

This pull request includes changes to the .goreleaser.yml file to update the nfpms section by replacing the builds key with the ids key for specific entries. The most important changes are as follows:

• Changed nfpms entry for dfget to use ids instead of builds. (.goreleaser.yml .goreleaser.ymlL142-R142)
• Changed nfpms entry for dfcache to use ids instead of builds. (.goreleaser.yml .goreleaser.ymlL188-R187)
• Changed nfpms entry for dfstore to use ids instead of builds. (.goreleaser.yml .goreleaser.ymlL232-R230)

Related Issue

Motivation and Context

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation Update (if none of the other choices apply)

Checklist

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 34.51%. Comparing base (8eed7f6) to head (8badd26).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3943      +/-   ##
==========================================
- Coverage   34.51%   34.51%   -0.01%     
==========================================
  Files         339      339              
  Lines       39937    39937              
==========================================
- Hits        13786    13785       -1     
- Misses      25243    25244       +1     
  Partials      908      908              

Flag	Coverage Δ
unittests	34.51% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.