Fix issues with cargo-update workflow (#1244)

* Fix issues with cargo-update workflow

This patch addresses many little issues:

- The backtick (`) character was being interpreted as shell expansion in
  the `git commit` command
- The `noreply` email for `phylum-bot` did not include the user ID
- This repository does not use Conventional Commits, so the `build:`
  prefix was unnecessary

* Use "phylum-bot" for committer name

Co-authored-by: Charles Coggins <maxrake@users.noreply.github.com>

---------

Co-authored-by: Charles Coggins <maxrake@users.noreply.github.com>

.github/workflows/cargo-update.yml

@@ -21,9 +21,9 @@ jobs:
         id: commit
         continue-on-error: true
         run: |
-          git config user.name 'Phylum Bot'
-          git config user.email 'phylum-bot@users.noreply.github.com'
-          git commit -a -m "build: Bump `Cargo.lock` dependencies"
+          git config user.name 'phylum-bot'
+          git config user.email '69485888+phylum-bot@users.noreply.github.com'
+          git commit -a -m "Bump dependencies"
           git push --force origin HEAD:auto-cargo-update
 
       - name: Create Pull Request
@@ -37,6 +37,6 @@ jobs:
               repo: context.repo.repo,
               head: "auto-cargo-update",
               base: context.ref,
-              title: "build: Bump `Cargo.lock` dependencies",
-              body: "Bump dependencies in `Cargo.lock` for all SemVer-compatible updates.",
+              title: "Bump dependencies",
+              body: "Bump dependencies for all SemVer-compatible updates.",
             });