GH-48025: [C++][GLib] Replace instances where build path is being added to built artifacts

[raulcd]

Rationale for this change

There are several places where we are adding the build path on our built artifacts. We should avoid that in order to improve reproducibility of our builds.

What changes are included in this PR?

General build system hygiene improvement redacting absolute paths from the compiler flags to improve build reproducibility and caching efficiency.

Update for mkenums from full @filename@ to @basename@ as seen on their official documentation:

The base name of the input file currently being processed (e.g. foo.h). Typically you want to use @basename@ in place of @filename@ in your templates, to improve the reproducibility of the build. (Since: 2.22)

Are these changes tested?

Validated locally that reprotest doesn't fail on enums anymore.

CI and tests have run.

Are there any user-facing changes?

No

• GitHub Issue: [C++][GLib] Remove build_path being added to our generated files on build #48025

[github-actions]

⚠️ GitHub issue #48025 has been automatically assigned in GitHub to PR creator.

[raulcd]

As far as I understand failures are unrelated. Examples:

• [CI][C++] ARM64 macOS 14 C++ fails on Substrait.ArrowSpecificLiterals test #47957
• [CI][Ruby][Flight] flight-sql test fails on PRs with invalid SQL #47842

I am unsure on what is the problem on C GLib & Ruby / AMD64 Ubuntu 22.04 GLib & Ruby but does not seem related:

 + ruby test/run-test.rb
/arrow/c_glib /
/var/lib/gems/3.0.0/gems/test-unit-3.7.0/lib/test/unit/util/backtracefilter.rb:16:in `method': undefined method `start' for class `#<Class:PowerAssert>' (NameError)
	from /var/lib/gems/3.0.0/gems/test-unit-3.7.0/lib/test/unit/util/backtracefilter.rb:16:in `<module:BacktraceFilter>'
	from /var/lib/gems/3.0.0/gems/test-unit-3.7.0/lib/test/unit/util/backtracefilter.rb:9:in `<module:Util>'
	from /var/lib/gems/3.0.0/gems/test-unit-3.7.0/lib/test/unit/util/backtracefilter.rb:8:in `<module:Unit>'
	from /var/lib/gems/3.0.0/gems/test-unit-3.7.0/lib/test/unit/util/backtracefilter.rb:7:in `<module:Test>'
	from /var/lib/gems/3.0.0/gems/test-unit-3.7.0/lib/test/unit/util/backtracefilter.rb:6:in `<top (required)>'
	from /var/lib/gems/3.0.0/gems/test-unit-3.7.0/lib/test/unit/assertions.rb:7:in `require_relative'
	from /var/lib/gems/3.0.0/gems/test-unit-3.7.0/lib/test/unit/assertions.rb:7:in `<top (required)>'
	from /var/lib/gems/3.0.0/gems/test-unit-3.7.0/lib/test/unit/testcase.rb:12:in `require_relative'
	from /var/lib/gems/3.0.0/gems/test-unit-3.7.0/lib/test/unit/testcase.rb:12:in `<top (required)>'
	from /var/lib/gems/3.0.0/gems/test-unit-3.7.0/lib/test/unit/autorunner.rb:7:in `require_relative'
	from /var/lib/gems/3.0.0/gems/test-unit-3.7.0/lib/test/unit/autorunner.rb:7:in `<top (required)>'
	from <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:96:in `require'
	from <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:96:in `require'
	from test/run-test.rb:113:in `<main>'

[kou]

The "undefined method" error will be fixed soon in upstream: test-unit/test-unit#329

[kou]

+1

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 0 benchmarking runs that have been run so far on merge-commit 534ef71.

None of the specified runs were found on the Conbench server.

The full Conbench report has more details.