Correct 'engines' property in package.json to align with other Auro projects

[MattSidor]

Alaska Airlines Pull Request

Changed the allowed version ranges of node in "engines" property of package.json to allow versions 12+ to install the project.

Fixes: #60

Summary:

This aligns with other recently-updated Auro projects that specify the "engines" property.

Type of change:

Please delete options that are not relevant.

• [ ] New capability
• [ ] Revision of an existing capability
• [ ] Infrastructure change (automation, etc.)
• [X] Bug

This affects consumers who wish to npm install the library, or contributors who wish to work on it in their local development environment.

Checklist:

• [X] My update follows the CONTRIBUTING guidelines of this project
• [X] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[MattSidor]

You're right, I copied the example; I misunderstood the purpose of what goes in the parentheses. What does "pencil" refer to in that example exactly? For my future PRs, how do I find out what to put in for the scope, or is it subjective? I wouldn't have known to use "package" for this one.

[AuroDesignSystem]

:tada: This PR is included in version 1.1.10 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: