Fix issue where replacement text is not getting evaluated when pack

[joperezr]

Description

During our build, we currently are running Pack again after running tests (which is wrong and fixing it is tracked by #5404). Because of that, and due to a recent change that caused a new Restore operation to be called when sending our tests to Helix, the build is now trying to re-run pack one the package that was restored during test runs, but it is doing so by passing /p:Restore=false /p:Build=false. Currently, our ReplacementText targets only run if you are running the Build target as well, but if you run Pack and skip the Build, then the replacement targets won't run, meaning the new generated package won't have the placeholders replaced, which is what is causing #5396 to happen. This change is making it so that our Replacement targets also are hooked into the Pack target even when Build gets skipped which will workaround the issue. The ultimate fix will be to not try to re-pack the projects after testing, which will be tracked by #5404.

Fixes # #5396

cc: @eerhardt @radical

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue:
  • No

Microsoft Reviewers: Open in CodeFlow

[radical]

Waiting on the internal build for validation.

[joperezr]

Found an issue with the initial approach as that was causing even more packages to get re-built post testing, which was causing other packages to be incorrectly built. This new approach is rolling that back and instead just avoiding causing a rebuild at all in that last pack call by no longer depending on restore when sending the tests to helix

[joperezr]

I have validated with the internal build that this is working as expected. This is ready to go.

[joperezr]

/backport to release/8.2

[github-actions]

Started backporting to release/8.2: https://github.com/dotnet/aspire/actions/runs/10536228450