Use the new scim-trace feature from our fork of laravel-scim-server lib

[uberbrady]

We have had a lot of SCIM issues of late, which have been hard to track down. This change enables us to use the newest version of our own fork of the laravel-scim-server library, which now has a scim-tracing feature which will write (almost) every single request and response that comes from SCIM into its own log file. (Requests against non-existent resources still will get caught at the routing layer, due to route-model binding, so we can't catch those just yet. But they will show up in laravel.log and will be pretty apparent).

@snipe had expressed some concerns about whether or not we would have to add the new scim.log file to the .gitignore - but it's not showing up as changed on my local so that seems fine already. She also talked about the idea of adding an empty scim.log file to the ./storage/logs directory - but I fear this is going to make the file be 'tracked by git' so I'm going to not add that just yet. But if you have the Linux chops to be able to twiddle the .env to add your SCIM_TRACE variable to it, then you can just as easily do a touch on that file, I figure.

If it turns out that this latest change to the composer.lock file actually blows things up, we can just do a simple revert and it should pull us back to the prior release, so that should keep us relatively safe.