remove config id from build data to avoid action conflict errors

Author: rickeylev

python/private/build_data_writer.sh

@@ -1,7 +1,6 @@
 #!/bin/sh
 
 echo "TARGET $TARGET" >> $OUTPUT
-echo "CONFIG_ID $CONFIG_ID" >> $OUTPUT
 echo "CONFIG_MODE $CONFIG_MODE" >> $OUTPUT
 echo "STAMPED $STAMPED" >> $OUTPUT
 if [ -n "$VERSION_FILE" ]; then

python/private/py_executable.bzl

@@ -1380,9 +1380,6 @@ def _write_build_data(ctx):
     ctx.actions.run(
         executable = ctx.executable._build_data_writer,
         env = {
-            # Include config id so binaries can e.g. cache content based on how
-            # they were built.
-            "CONFIG_ID": ctx.configuration.short_id,
             # Include config mode so that binaries can detect if they're
             # being used as a build tool or not, allowing for runtime optimizations.
             "CONFIG_MODE": "EXEC" if _is_tool_config(ctx) else "TARGET",