Forced user_id and role_id for roles relationship

I choose to not make my own Role and Permission model and just use your EntrustRole and EntrustPermission directly instead.

The issue here is that eloquent will infer the column names from the class name hence trying to set attached_roles.entrust_role_id

By enforcing the column names we get around this issue without any considerable downsides in my opinion.
Merge pull request #176 from AndreasHeiberg/patch-1

Forced user_id and role_id for roles relationship
Changed the migration template.

https://github.com/Zizaco/entrust/pull/151
Merge pull request #181 from gayanhewa/patch-1

Changed the migration template.
Revert "Changed the migration template."
Merge pull request #183 from Zizaco/revert-181-patch-1

Revert "Changed the migration template."
Allow usage with laravel 5 too
Merge pull request #194 from thoughtsatire/patch-1

Allows L5 usage.
Change readme for forum post to new laravel.io
Merge pull request #195 from andrewelkins/patch-1

Change readme for forum post to new laravel.io
Update composer.json
Update composer.json
Merge pull request #198 from andrewelkins/master

Change to my ardent so it'll work with L5
Update to use Laravel 5 development
Changing to 1.3

This is actually a fairly interesting change do to the addition of 
```
"minimum-stability": "dev"
```
Merge pull request #199 from andrewelkins/patch-1

Update to use Laravel 5 development
Merge branch 'master' into 2.0-dev

Conflicts:
	composer.json