update staging.yaml

[ci skip]

@NoahCarnahan I renamed the branch to the cononical name and force
pushed. No point in preserving old merge branches if you're replacing
them with a more up-to-date merge
update staging.yaml

[ci skip]

@NoahCarnahan @nickpell removing graphing branches because they're
already merged into case-detail-tabs
Merge branch 'double-management+case-detail-tabs' into autostaging
Merge branch 'ptop-reindex' into autostaging
Merge branch 'historical-forms' into autostaging
Merge branch 'remove-hutch' into autostaging
Merge remote-tracking branch 'origin/subscription-no-contact-info' into autostaging
Merge remote-tracking branch 'origin/revert-4574-revert-4553-case-list-redesign' into autostaging
Merge remote-tracking branch 'origin/revert-4205-revert-3841-86347-2' into autostaging
Merge remote-tracking branch 'origin/masterlist-workflow' into autostaging
Merge remote-tracking branch 'origin/bulk-app-translate' into autostaging
Merge remote-tracking branch 'origin/share-fixtures' into autostaging
Merge remote-tracking branch 'origin/logos' into autostaging
Merge remote-tracking branch 'origin/hq-dropdown' into autostaging
Merge remote-tracking branch 'origin/142623-jstree-upgrade' into autostaging
Merge remote-tracking branch 'origin/fix-user-indicators' into autostaging
Merge remote-tracking branch 'origin/custom-data-choices' into autostaging
update submodule refs