Changed default behavior about clockwork

[DominicDetta]

This is my mistake despite the issue has been resolved by @UlrichEckhardt.
I set default to false because we want probably use clockwork in production but for a very brief moment and of course with authentication. I'm aware of the danger. I didnt want to remember to disable clockwork.. I know I'm a lazy person.
No problem if you want to revert this value to be true by default.

[fedorovsergey]

I suppose you right, it would be more clear when developer must enable the plugin explicitly in config or other way.
I just wanted to point out that previous behavior has changed, and may be instructions or setup guid or smth should reflect these changes

[itsgoingd]

Hey, this was indeed not intentional. I will update this to be the same as in Laravel integration - enabled by default only on local domains (localhost, .local, .test, .wip and 127.0.0.1).