ci: use the shared angr/binaries ref action

[zardus]

THIS MESSAGE WAS GENERATED BY AN AUTOMATED PROCESS

#738 added twenty-two lines of shell to ci.yml to resolve which angr/binaries revision a build should use. The same block is now wanted in angr, pysoot and angr-management, so it has been extracted into a composite action in angr/ci-settings rather than pasted into each one. This replaces cle's copy with a call to it; the behaviour and the checkout step are unchanged.

Blocked on angr/ci-settings#123, which adds the action; this references it at master.

[zardus]

THIS MESSAGE WAS GENERATED BY AN AUTOMATED PROCESS

The failing jobs all stop in Set up job, before any checkout or test runs:

Can't find 'action.yml', 'action.yaml' or 'Dockerfile' for action 'angr/ci-settings/actions/binaries-ref@master'

That is the expected state while angr/ci-settings#123 is open: this references the action at master, where it does not exist yet. The red is not a property of this diff and there is nothing here to repair. Merging angr/ci-settings#123 and re-running the whole run clears it.

The workflow file was checked with yaml.safe_load before pushing, and the resolution logic itself was exercised against five pull-request body forms in angr/ci-settings#123.

[angr-bot]

Corpus decompilation diffs can be found at angr/dec-snapshots@master...angr/cle_779