Add build assets to source control

[stevehobbsdev]

Changes

This PR allows the Lock build assets to be added to source control, which solves an issue with our build process where the build/ folder does not appear in the release package. This is used by those customers using Bower to consume our library, whilst also allowing our automated release system to work.

Previously the build files were force-commited just-in-time when making a release PR, but this has problems when working on the codebase post-release, as Git just wants to remove these files again, and the whole thing gets a bit messy.

References

Testing

• This change adds unit test coverage
• This change adds integration test coverage
• This change has been tested on the latest version of the platform/language

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All code quality tools/guidelines have been run/followed
• All relevant assets have been compiled

[lbalmaceda]

LGTM. QQ; Do these files change again when you run yarn dist build without further changes?

[stevehobbsdev]

@lbalmaceda They may do but they should also be auto-collapsed in the diff when reviewing a PR so hopefully they won't add too much noise.