Add reusable workflows structure, RW pre-commit, RW DangerJS, RW Sync Jira (3pack)

[tomassebestik]

Caution

Back in Draft - please hold off on your review.
Although this works, there might be a more elegant way by storing only "call-<reusable_workflow>" type actions here, and defining the reusable workflow in the repository of the action (e.g., https://github.com/espressif/sync-jira-actions).

---

---

This PR creates the structure for using GitHub reusable workflows that can be called from any repository within the Espressif GitHub organization.

Note

Their presence here does not mean they are automatically propagated or inherited across all Espressif organization GitHub repositories (as with issue and pull request templates).

These workflows need to be explicitly called.
See the .github/workflows/workflows-instructions.md (part of this PR) for more details.

Reasoning / Why This

Managing these workflows from a central place like this repository (espressif/.github) offers several advantages:

• Ease of Integration: Simplifies the process for repository administrators—only a call statement is needed to integrate the workflow.
• Centralized Updates: Quickly update the version of a GitHub workflow for all repositories that use it with a single change here.
• Consistent Permissions: Ensure that action permissions are set correctly across all repositories.

Reusable Workflows in This PR

• Configurable pre-commit reusable workflow
• Configurable dangerjs reusable workflow
• Configurable jira-sync reusable workflows (issues, pull requests, issue comments)
• Instruction guide .github/workflows/workflows-instructions.md with example calls from target project

---

Tested

Tested in my test GitHub organization:

• test org .github repo - where reusable workflows are defined
• test org target repo - where reusable workflows are called - code
• test org target repo - where reusable workflows are called - action run ✔️

[tom-borcin]

LGTM!