Fix Contact 'email' property filtered due to 'Emails' HubSpot type

[leolll]

This PR addresses an issue where the email property was being incorrectly filtered out due to a conflict with the Emails HubSpot type. This was causing a sales-email-read scope error when attempting to access $contact->email, as the code was inadvertently trying to access the $contact->emails associated type instead.

Changes:

• Added an isAllowedProperty method to centralize property filtering logic
• Updated fill and __set methods to use isAllowedProperty
• Specifically allowed email property while maintaining filtering for other HubSpot types

This fix ensures that:

1. The email property is correctly retained and accessible
2. The code no longer attempts to access the Emails associated type when simply trying to get the email property from a Contact
3. The sales-email-read scope error is avoided for email property access

The original intent of filtering out most HubSpot types is maintained, while solving this specific edge case.

This change should resolve issues for users who were encountering unexpected scope errors when working with contact email addresses.

Bug Demonstration

Currently, if you run this code:

$contact = Contact::find(555);
echo $contact->email;

email is not defined. This is because email when pluralized (src/Api/Model.php line 85) is a HubSpot associated type of Contact. It also triggers an attempt to download the Contact's associated Emails, which can lead to unexpected behavior and potential sales-email-read scope errors.

[jszobody]

This makes sense, I'm surprised I haven't run into it myself.

Can you take a quick look at the failing tests and see about fixing those?

[jszobody]

Thanks!

[leolll]

No problem! Thanks for the great package.