BUG: Session schema truncates long list of scopes.

Issue summary

Getting this error:

Failed to save session to database: SQLSTATE[22001]: String data, right truncated: 7 ERROR: value too long for type character varying(255)

The list of scopes being saved is:

read_locations,read_price_rules,read_product_listings,write_assigned_fulfillment_orders,write_customers,write_draft_orders,write_fulfillments,write_inventory,write_merchant_managed_fulfillment_orders,write_order_edits,write_orders,write_products,write_returns,write_third_party_fulfillment_orders

...which is 296 characters.

Adding this migration to fix, appears to work:

        Schema::table('sessions', function (Blueprint $table) {
            $table->text('scope')->nullable()->change();  // Don't impose a length limit
        });

Expected behavior

Session should save the scope list however long it is.

Actual behavior

Failed to save session to database: SQLSTATE[22001]: String data, right truncated: 7 ERROR: value too long for type character varying(255)

Steps to reproduce the problem

1. Put a long list of scopes (> 255 chars) in your TOML and deploy
2. Attempt to use the app
3. Get 500 error, SQL truncation error in log

NOTE: This issue probably applies to other app templates as well. They should be reviewed.

Locate the sessions table schema and the migration entry point that defines the scope column, then review how the TOML scope list is persisted. Reproduce with a scope list over 255 characters and verify that the schema accepts it without the PostgreSQL truncation error; review the other app templates as noted.