tenant support logic added.

[what-the-diff[bot]]

PR Summary 📚

• Adding a New Configuration Added a new configuration to identify which model (in our case, it's the 'Team' model) is responsible for handling multi-tenancy. This means having different groups of users with specific privileges within the same application. 🔄

• Data Model Update Tweaked the 'filament_email_log' database table to include a new column 'tenant_id'. This helps keep track of which team (tenant) a specific email belongs to. This field may sometimes be empty, which is just fine by the system! 🗃️

• Improving Logging Enhanced the logging system. Now, it not only logs the events but also knows who initiated the event - either a tenant (team) or a regular authenticated user. This is a fancy way of saying we now know who did what! 🕵️‍♂️👀

• Getting Connected Introduced a new 'Team' relationship to the 'Email' model. This basically means, now each email is associated with a team and vice versa. Emails love to have buddies! 💌❤️

• Upgrading 'Boot' Method Tweaked the 'boot' method in the 'Email' model. Boot methods are called when the model is being brought into action. Our method is now even better at its job! 🚀

[marcogermani87]

Hi @nilede-bharat, thanks for PR; i need to review some code to store attachments into specific team_id folder and doing some tests before merging this.