Remove another attempt to cache target directory in action.yaml

[alamb]

Which issue does this PR close?

re #2149

Rationale for this change

I removed most of the ineffective "try to cache target" logic in #2150 but I missed one

I noticed this while looking at the failure here: https://github.com/apache/arrow-rs/runs/7500811391?check_suite_focus=true

It basically runs out of disk space when trying to copy all of target into the cache (and it took 3m to do so)

What changes are included in this PR?

Remove attempt to cache target directory from common setup-builder action

Are there any user-facing changes?

Hopefully less CI failures due to out of disk space

[alamb]

Here is another example of burning 2 minutes on what is already the longest job (test workspace): https://github.com/apache/arrow-rs/runs/7498748655?check_suite_focus=true

[alamb]

Ouch here is one job that took 7 minutes to do the post cache: https://github.com/apache/arrow-rs/runs/7501158692?check_suite_focus=true

[ursabot]

Benchmark runs are scheduled for baseline = ada108b and contender = 13e6f39. 13e6f39 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ursa-thinkcentre-m75q] ursa-thinkcentre-m75q
Buildkite builds:
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java