🔨 Add profile to cargo-build composite action

The `cargo-build` composite action is currently always building the
default profile, rather than specifying a profile. It will eventually
be necessary to state `"dev"` vs `"release"`, so this attempts to
address this now by creating a workflow parameter that can be specified.

By default, this will still build `dev`.

.github/actions/cargo-build/action.yaml

@@ -1,5 +1,10 @@
 name: cargo-build
 description: "Performs a cargo build, with caching"
+inputs:
+  profile:
+    default: dev
+    description: "The build profile to use"
+    required: false
 
 runs:
   using: "composite"
@@ -15,11 +20,14 @@ runs:
       uses: actions/cache@v3
       with:
         path: target
-        key: cargo-build-${{ runner.os }}-${{ hashFiles('frameworks/**/*.rs', 'alloy/**/*.rs', 'example/**/*.rs', '**/Cargo.toml', 'Cargo.toml') }}
+        key: cargo-build-${{ inputs.profile }}-${{ runner.os }}-${{ hashFiles('frameworks/**/*.rs', 'alloy/**/*.rs', 'example/**/*.rs', '**/Cargo.toml', 'Cargo.toml') }}
 
     - name: Build
       if: steps.cargo-build.outputs.cache-hit != 'true'
       shell: bash
       run: |
-        cargo build --verbose --message-format json                            \
+        cargo build                                                            \
+          --verbose                                                            \
+          --profile ${{ inputs.profile }}                                      \
+          --message-format json                                                \
           | cargo-github-annotation