[DynInst_API:] [dyninst/dyninst] 5cd8fb: GithubCI: only build hpctoolkit@develop

[Tim Haines <noreply@xxxxxxxxxx>]

  Branch: refs/heads/thaines/githubci_hpctoolkit
  Home:   https://github.com/dyninst/dyninst
  Commit: 5cd8fb26dcb360b8fae48d187bfde1adfb13e977
      https://github.com/dyninst/dyninst/commit/5cd8fb26dcb360b8fae48d187bfde1adfb13e977
  Author: Tim Haines <thaines.astro@xxxxxxxxx>
  Date:   2024-01-10 (Wed, 10 Jan 2024)

  Changed paths:
    M .github/workflows/consumers.yaml

  Log Message:
  -----------
  GithubCI: only build hpctoolkit@develop

Building the HEAD of dynininst against the last release of HPCToolkit
is a good idea for tracking breaking changes, but it ultimately
produced more noise than signal. Making sure that HPCToolkit's latest
source will compile with Dyninst's latest source is likely a better
measure.