🐞 Describe the bug
My team needs to pass runtime environment variables to vercel deploy: https://vercel.com/docs/cli/deploy#env

📚 To Reproduce
Attempt to add --env using this action.

💡 Expected behavior
It is possible.

🖼️ Screenshots
It is not currently possible.

⚙️ Environment
Action version: v1.10.0

📋 Additional context
Our work-around is to add BUILD_ENV instead, and then use next.config.js to make certain vars available at runtime, e.g.

// pass build env through to runtime until deploy-to-vercel-action adds support for --env
env: {
  NEXT_PUBLIC_ID1: process.env.NEXT_PUBLIC_ID1,
  NEXT_PUBLIC_ID2: process.env.NEXT_PUBLIC_ID2,
  ...
}