Inputs are not resolved for docker build args

[Greven145]

🔥 Bug Description

When an input is used as a reference for the value of a buildArg, the value is not replaced in the docker build command

🔍 Steps to Reproduce the Bug

1. Start with an app host project with a parameter and a container resource

   var builder = DistributedApplication.CreateBuilder(args);
   
   var npmToken = builder.AddParameter("npmToken", secret: true);
   builder.AddNpmApp("client", "../aspirate-buildargs-bug.Client")
           .PublishAsDockerFile([
               new DockerBuildArg("NPM_TOKEN", npmToken.Resource)
           ]);
   
   builder.Build().Run();

2. Generate the manifest

   {
     "resources": {
       "npmToken": {
         "type": "parameter.v0",
         "value": "{npmToken.inputs.value}",
         "inputs": {
           "value": {
             "type": "string",
             "secret": true
           }
         }
       },
       "client": {
         "type": "dockerfile.v0",
         "path": "../aspirate-buildargs-bug.Client/Dockerfile",
         "context": "../aspirate-buildargs-bug.Client",
         "buildArgs": {
           "NPM_TOKEN": "{npmToken.value}"
         },
         "env": {
           "NODE_ENV": "development"
         }
       }
     }
   }

3. Run aspirate build

     $ aspirate build -m manifest.json
     
          _                    _           ___  
         / \     ___   _ __   (_)  _ __   ( _ ) 
        / _ \   / __| | '_ \  | | | '__|  / _ \ 
       / ___ \  \__ \ | |_) | | | | |    | (_) |
      /_/   \_\ |___/ | .__/  |_| |_|     \___/ 
                      |_|                       
     Handle deployments of a .NET Aspire AppHost
     
     
     ── Handling Aspirate State ─────────────────────────────────────────────────────────────────────────────
     Loading state from 
     <snip file path>/aspirate-buildargs-bug/aspirate-buildargs-bug.AppHost/aspirate-state.json.
     Would you like to use all previous state values, and skip re-prompting where possible ? [y/n] (y): y
     (✔) Done:  State loaded successfully from 
     <snip file path>/aspirate-buildargs-bug/aspirate-buildargs-bug.AppHost/aspirate-state.json. Will run 
     without re-prompting for values.
     
     ── Handling Aspirate Secrets ───────────────────────────────────────────────────────────────────────────
     Secret State have been loaded, but the current command does not need to decrypt them.
     
     ── Handling Aspire Manifest ────────────────────────────────────────────────────────────────────────────
     Aspire Manifest supplied at path: manifest.json.
     Skipping Aspire Manifest generation.
     
     ── Selecting Required Components ───────────────────────────────────────────────────────────────────────
     Processing all components in the loaded file, as per the state file.
     
     ── Gathering Information about deployables ─────────────────────────────────────────────────────────────
     No project components selected. Skipping execution of container detail gathering for them.
     No project components selected. Skipping execution of container detail gathering for them.
     
     ── Handling Projects ───────────────────────────────────────────────────────────────────────────────────
     No project components selected. Skipping build and publish action.
     
     ── Handling Dockerfiles ────────────────────────────────────────────────────────────────────────────────
     (✔) Done:  Setting container details for Dockerfile client
     
     Executing: docker build --tag "client:latest" --build-arg NODE_ENV="development" --build-arg 
     NPM_TOKEN="{npmToken.value}" --file 
     "<snip file path>/aspirate-buildargs-bug/aspirate-buildargs-bug.Client/Dockerfile" 
     ../aspirate-buildargs-bug.Client
    <snip docker stuff>
     
      🚀 Execution Completed 🚀

🧯 Possible Solution

Resolve the build arguments as potential reference values like other resource manifest references