Create infra for Appointment Planner API

[willmcvay]

Background context or User story:

The Appointment Planner Component has it's own API. It will aggregate available viewing slots and return to the Appointment Planner

Specification or Acceptance Criteria:

• Depends on Address confusing structure in web components #1218 should live in the AppointmentPlanner/server folder
• Needs to be registered as an application, have it's own client id and API key
• Needs to have isWebComponent set as a boolean on the app via Postman
• Needs permissions to Read: appointments, offices, negotiators
• Should have an express app with 2 routes - a ping see Cypress test for production environment by cronjob and alert to slack if error #1221 and a route GET /appointment-slots
• Task is to scaffold a Lambda and add to the web components Serverless deployment

[duong-se]

hi @willmcvay, cloud you help me to delete this stack and I'll try to re-deploy it again. Because I dont have permission to delete IamRoleLambdaExecution

The following resource(s) failed to delete: [IamRoleLambdaExecution].