feat: create new CasbinRule instance every time sequelize Adapter opens connection

[tsoultanopoulos]

Fix: #78

Why?
Previously, the system utilized multiple adapters to establish connections with different databases based on their respective schemas. However, there was an unintended behavior where the last adapter defined in the configuration would override the previous ones, resulting in only a single database connection being used, regardless of the schema.it supposed that was solved with this PR but the issue still persists.
What was changed?
In the updated code, a new CasbinRule model is dynamically created for each Sequelize adapter instance with the createCasbinRule function. This function generates a custom CasbinRule model class with its own tableName and schema options. This ensures that different Sequelize adapters have isolated configurations, avoiding potential clashes when multiple adapters are opened with different table names or schemas.

[casbin-bot]

@nodece @Zxilly @Shivansh-yadav13 please review

[CLAassistant]

All committers have signed the CLA.

[hsluoyz]

@nodece plz review

[hsluoyz]

@tsoultanopoulos fix:

[coveralls]

Pull Request Test Coverage Report for Build 5358173782

• 14 of 14 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.09%) to 86.061%

---

Totals
Change from base Build 4439363605:	0.09%
Covered Lines:	117
Relevant Lines:	126

---

💛 - Coveralls

[github-actions]

🎉 This PR is included in version 2.7.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀