Bugfix: The resource name for the HTTP Event AWS generates contains the lambda name twice

[MartinRamm]

During the deployment, AWS first creates the new resource and the deletes the old one. Therefore, this fix does not cause any sort of downtime. It should also be backwards compatible, unless someone relies on the HTTP event name schema while overriding the cloudformation template in the deploy.start hook.

This fixes architect/architect#1487

Thank you for helping out! ✨

We really appreciate your commitment to improving Architect

To maintain a high standard of quality in our releases, before merging every pull request we ask that you've completed the following:

• Forked the repo and created your branch from main
• Made sure tests pass (run npm it from the repo root)
• Expanded test coverage related to your changes:
  • Added and/or updated unit tests (if appropriate)
  • Added and/or updated integration tests (if appropriate)
• Updated relevant documentation:
  • Internal to this repo (e.g. readme.md, help docs, inline docs & comments, etc.)
  • Architect docs (arc.codes)
• Summarized your changes in changelog.md
• Linked to any related issues, PRs, etc. below that may relate to, consume, or necessitate these changes

Please also be sure to completed the CLA (if you haven't already).

Learn more about contributing to Architect here.

Thanks again!