Alternative trait instead of extending class

[matthew-inamdar]

Following the proposal of #20, we should definitely add a trait as an alternative to extending the classes provided.

This flexibility allows this package to still be utilised in the event that the client code is already extending their models from a class provided in another package.

This will need to be documented in the README.md.

[firmantr3]

That would be nice! 👍

[matthew-inamdar]

@firmantr3 I've created a PR to add trait support. Please check out the docs and give feedback:

Docs: https://github.com/goldspecdigital/laravel-eloquent-uuid/blob/feature/trait/README.md
PR: #22