fix(inputs): add fallback to ENV for inputs JIRA_COMPONENT and JIRA_TASK

[tomassebestik]

Description

The Jira component defined in the target project workflow doesn't take effect (sync runs, but ticket created with empty component).

In our target projects, workflows are mostly set as ENV, but the action file (action.yml) is missing a fallback option for reading the value of JIRA_COMPONENT from ENV (same for JIRA_ISSUE_TYPE).

This is a quick patch. The entire GitHub Action is planned for a complete refactor very soon.

Related

• Internal ticket RDT-930 (all code of this repo refactor)
• Reported in espressif/esp-video-components#12 by @wujiangang

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello tomassebestik, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against a62c766

[wujiangang]

LGTM