Don't require authentication when running locally

The authentication required to run this plugin entails creating a new user, granting them the required capability, and generating an application password. Finally, running the pattern library capture locally requires exporting the user name and application password as constants.

This security model makes sense for a live/deployed environment, but for running locally, it's overkill.

It would be nice to bypass authentication when the environment type is "local", so that developers can build a pattern library locally without going through all of these steps.

Start at the entry point that determines the environment type and configures authentication for pattern library capture. Verify how local credentials are currently required, then make local captures work without authentication while retaining authentication for deployed environments. Done means developers can run the local capture without creating a user or exporting credentials, and deployed behavior is unchanged.

Written by the indexing model from the issue text.