[Enhancement] - [Add Build Tool Name to Each Command in build_commands Section of Buildspec]

[behnazh-w]

Description

Currently, the build_commands section of the generated buildspec lists the commands as arrays, but does not explicitly indicate which build tool each command corresponds to. This can make it harder for downstream users to quickly understand and associate commands with their respective tools, especially when multiple build tools are invoked.

Proposed Feature

Enhance the buildspec generation so that each entry in build_commands includes an explicit tool field. For example:

"build_commands": [
  {
    "tool": "hatch",
    "command": ["hatch", "build"]
  },
  {
    "tool": "pip",
    "command": ["python", "-m", "build", "--wheel", "-n"]
  }
]

Also, it would be good to indicate build tool version used in the project's release scripts., maybe even for maven or pypi. Especially with Gradle which is rapidly evolving, it would be good to get the desired version in the buildspec. It can be easily parsed out of the gradle-wrapper.properties in case gradlew is present, but some projects still do not use the wrapper - and the situation is more complicated there - some heuristic is needed.

Use Case

Tooling and automation systems that need to identify which build tool was used for a particular command.