chore: Add CHANGELOG configuration

[embano1]

Description

Configuration for creating a CHANGELOG file and release annotation in upcoming releases. Will be used by Github Actions.
Currently the following commit title prefixes are defined as highlighted sections:

• feat: - Feature
• fix: - Bug Fix
• chore: - Chore/Repo activities

Example:

v0.2.0

Release Date: 2021-05-07

🧹 Chore

• Add CHANGELOG configuration
• Verify PRs and push to main
• Add stale action

📖 Commits

• chore: Add CHANGELOG configuration [5764180]
• Add PR template [a0e1078]
• Update issue templates [ae6f848]
• Improve examples. Remove unnecessary details. [3a9010a]
• Implement wait server to start in the integrations tests BeforeAll Fix Binary Mode HTTP Header DateTime format. It is UTC time formatted in ISO 8601 format including milliseconds. Bump revision of the module version [401a475]
• chore: Verify PRs and push to main [0bd4192]
• chore: Add stale action [e08a275]
• Add Install Module Instructions to README (#17) [3629c77]
• Enable process exit in build.ps1 [aac584a]
• Create CONTRIBUTING.md (#15) [84606b0]
• Renames Add-CloudEventData to Set-CloudEventData (#12) [d305f16]
• Adds license headers in source code files (#11) [f23df54]
• Remove install instructions from an internal PS repository (#10) [62f14b6]
• Initial commit [b2afcf8]

Closes: #29
Signed-off-by: Michael Gasch mgasch@vmware.com

Type of change

Please mark options that are relevant:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to
  not work as expected)
• This change requires a documentation update

How Has This Been Tested?

$ git-chglog --next-tag v0.2.0 v0.2.0

Test Configuration:

• Toolchain:
• SDK:
• (add more if needed)

Checklist:

• My code follows the contribution
  guidelines
  of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules