added more information on running composer update when upgrading to 4.1

I had a different outcome when upgrading on a different server (shared hosting). I thought to share how I was able to circumvent that issue. Apparently, `composer update --no-scripts` doesn't always work. Though, running `composer update --no-scripts` did the trick on my local server at home.

Ravi.
I will rename app.conf to app.php. In some environments, simply running `composer update --no-scripts` does not work. There might be the need to edit app/config/app.php to resolve the issue with Class not found for Controller. This upgrade from 4.0 to 4.1 affects Controllers. What do you mean by "...aren't required"? They are option if class loading didn't for Controllers wasn't fixed with `composer update --no-scripts`.