Use commit timestamps for plugin EP dev versions

[Edward Chen (edgchen1)]

Description

• Use commit timestamps for plugin EP dev versions
• Update set_plugin_ep_build_variables.py to use argparse

Motivation and Context

Python dev package versions were using only the commit date. This prevented packages from multiple commits on the same day from being published. Using a finer granularity (from day to seconds) should mitigate it. It's probably good enough if we only expect to publish from main and release branches.

[Copilot]

Pull request overview

This PR updates the plugin Execution Provider packaging/versioning flow in CI by switching dev-version derivation from a day-granularity commit date to a second-granularity commit timestamp, and modernizes the helper script’s CLI to use argparse.

Changes:

• Compute plugin EP dev versions using the Git commit Unix timestamp (%ct) formatted as UTC YYYYMMDDHHMMSS to reduce same-day version collisions.
• Migrate set_plugin_ep_build_variables.py from positional args to argparse flags.
• Update the Azure Pipelines template step to pass the new flags.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
tools/ci_build/set_plugin_ep_build_variables.py	Switch dev version generation to second-level commit timestamp and introduce argparse-based CLI parsing.
tools/ci_build/github/azure-pipelines/templates/set-plugin-ep-build-variables-step.yml	Update pipeline invocation to use the new flag-based script interface.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.