fix: Write webpack stats file to right place (so static assets can load)

[timmc-edx]

After the removal of paver, static assets build wasn't completing properly in edxapp -- static files were written to the correct directory in the assets volume (mounted under /edx/var) but the webpack-stats.json files were written to the test_root dir in the app container (under /edx/app). The service would fail on first page load as it failed to find the stats file, which is apparently used for locating resources.

The static assets build was also taking quite a long time and a lot of CPU, which is likely because we were doing the production-style build with full optimization.

• Set static-root environment variables so that webpack-stats.json is written to the right place. See staticRootLms and staticRootCms in webpack.common.config.js in edx-platform for where that default is set. Set both LMS/CMS vars for both lms and cms since there's some dependency of CMS on LMS in the logic (and both calls build both sets of files, for better or worse).
• Use npm dev build for reduced optimization (faster build).
• Use --settings devstack_docker in the Makefile call to collectstatic; I'm not actually sure what the impact of that is, but it's what was in the provisioning script's version of the call and I needed to deduplicate these calls.
• Have provision-lms.sh just call the Makefile so that there aren't two sources of truth on how to build static assets for edxapp.

Also:

• Use same spelling of --no-input for both calls (either works, just make it uniform)

Addresses #65

---

I've completed each of the following or determined they are not applicable:

• Made a plan to communicate any major developer interface changes (or N/A)

[UsamaSadiq]

I've tested the provision locally against this branch. All the static assets were built successfully and local endpoint also loaded up fine.

[UsamaSadiq]

The failing macos check will be fixed once the PR #58 is merged.