Remove cookie serialization

[snipe]

This is an attempt at removing the cookie serialization settings. We've tried this in the past and ended up breaking the API when testing, so this branch will need to be tested obviously.

[what-the-diff]

PR Summary

• Cookie Encryption Changes

  • The encryption process for cookies has been updated. Specifically, we've updated the serialization setting which dictates how the data within the cookies is handled. In our case, we've switched the setting from true to false to adhere to best practices and enhance our application's security.

• Changes In Authentication Service

  • We've made several updates to streamline our authentication service and ensure it aligns with the most recent version of the authentication library (Passport) we're using. These changes include:
    • Removing unnecessary function calls: Previous versions of Passport required a specific function call (Passport::routes()), however, with our upgrade, this is no longer necessary.
    • Modifying token expiration times: We've adjusted when each type of token (access tokens, refresh tokens, and personal access tokens) expires to ensure secure and efficient user authentication.
    • Deleting obsolete function: We've removed the Passport::withCookieSerialization() function call, as it is no longer essential with the latest Passport changes.

[marcusmoore]

I pulled down this down and clicked through the dashboard, browsed the asset table, and created an asset (while also adding a new model) and didn't run into any issues. As expected I had to delete my session file to get the develop branch working again.