feat: configure CI workflow to trigger on master branch

[Copilot]

The CI and semantic-release workflow was configured to trigger on main branch, but the repository uses master as its default branch. This prevented automated releases and CI checks from running on master branch commits.

Changes

• Updated .github/workflows/main.yml to trigger on master instead of main branch

This aligns the workflow with the repository's default branch, enabling:

• Automated CI testing on master branch commits
• Semantic-release automation for version management and npm publishing
• Consistent behavior with the reference casbin/casbin repository

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/casbin/casbin/contents/.github/workflows
  • Triggering command: /usr/bin/curl curl -s REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[bug] need to run CI and make semantic-release for new master branch commit</issue_title>
<issue_description>need to make semantic-release for new master branch commit, like this repo: https://github.com/casbin/casbin</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [bug] need to run CI and make semantic-release for new master branch commit #520

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}