ci: don't trigger rust ci for doc changes

[xudong963]

Which issue does this PR close?

Closes #.

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

[alamb]

🤔 I think that the prettier checks run for doc changes

https://github.com/apache/arrow-datafusion/blob/master/.github/workflows/dev.yml#L39-L57

Perhaps we can add the trigger condition for that job so the markdown is checked when md files are modified?

[xudong963]

I think prettier checks will run for doc changes, here we only don't trigger rust ci for doc changes.

[alamb]

Thank you @xudong963

[ursabot]

Benchmark runs are scheduled for baseline = 0f80bca and contender = 842bda3. 842bda3 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-datafusion-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-datafusion-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