Makes the EPP module use basenames rather than absolute paths for all
-file attributes / ?FILE macros when +deterministic is set. Previously,
EPP did not respect +deterministic in all scenarios, so build output
could still contain absolute paths.

Makes asn1ct_gen filter out potentially non-deterministic attributes
from generated .erl files when +deterministic is set.

Makes generated leex scanners only use basenames in generated -file
attributes, rather than absolute paths when +deterministic is set.

Makes generated yecc parsers use only basenames in generated -file
attributes rather than absolute paths when +deterministic is set.

Makes compile pass along the +deterministic flag for epp to utilise.

Makes test_lib avoid a crash if +deterministic is enabled to tests.
+deterministic strips the compilation options entirely, which test_lib
wasn't able to handle. Now, an empty list is returned in that case.

Add a --enable-deterministic-build to the configure script,
which sets ERL_DETERMINISTIC=yes throughout the relevant
Makefiles, which then invoke the relevant build stages with the
+deterministic option.

This addresses absolute paths being included in generated .erl files
and compiled .beam files that resulted in builds from different source
directories generating different artefacts (which is a component of the
issue in #4482).

I think it would make sense to make this the default at some stage, but
I've put the change behind a flag for now to decouple
making deterministic OTP builds possible from making them the default.

Having +deterministic set results in compiler options being
removed from the module info for modules where this options was used.
This may have other implications for users of OTP.

For tests themselves, +determinism is not set, since many test cases
depend on accessing the test module's compilation options, or other
features not available in deterministic mode, in order to configure
themselves. For tests of the determinism feature specifically,
+deterministic must be explicitly passed to the compiler within the
relevant test cases.