Add support for composite primary keys

[stoutput]

Describe the feature as you'd like to see it
There should be a way to specify composite primary keys on a model, either as a tuple or list:

class User(Model):
    __primary_key__ = ['user_id', 'email']
    # or,
    __primary_key__ = ('user_id', 'email')

What do we currently have to do now?
Masonite currently only supports single primary keys:

class User(Model):
    __primary_key__ = 'user_id'

• Is this a breaking change?

[josephmancuso]

Will need to modify some behavior in Masonite ORM to be able to support this.

Find

The find method will need to check if the record_id that is passed is a list AND if the primary keys are a list. If so then it should perform 2 where clauses (where key1 is value1 and key2 is value2)

Update

On the query builder there is an update method. Right now it is just checking the model primary key. We will need to refactor the code to the model where we pass the query builder into the model and leave the model responsible for setting the where clause. This will clean the code up a bit.

Save

The save method calls either update or create. The create method should be fine and the update method should be fine after the above section is changed.

Delete

The delete method is doing a similar where statement as the update method. This will need the same refactoring to move the where clause into the model class

After the above changes are done then the library will be able to do composite primary keys