Add MailSlurp certified connector

[jackmahoney]

This PR submits the MailSlurp API as a certified connection.

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

If this is your first time submitting to GitHub and you need some help, please sign up for this session.

• I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
• I attest that the connector works and I verified by deploying and testing all the operations.
• I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• I attest that I have added response schemas to my actions, unless the response schema is dynamic.
• I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
• If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

• I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
• Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
• Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
• If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

[jackmahoney]

@microsoft-github-policy-service agree [company="MailSlurp"]

[jackmahoney]

@microsoft-github-policy-service agree company="MailSlurp"

[vmanoharas]

Hi @jackmahoney,

Please fix below swagger validation errors.

##[error]Summary string contains any of the restricted characters [/<>%&?] ValuePath: /paths/1emails1{emailId}~1body/get/summary
##[error]Summary string contains any of the restricted characters [/<>%&?] ValuePath: /paths/1emails1{emailId}~1imap-flag-operation/post/summary
##[error]The 'version' property must have not empty value. ValuePath: /info/version
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/1attachments1{attachmentId}~1bytes/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/1emails1{emailId}1attachments1{attachmentId}/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/1emails1{emailId}~1body-bytes/get/responses/default
##[error]The 'name' property is required. ValuePath: /info/contact

[jackmahoney]

@vmanoharas thank you for reviewing my submission. I have made changes now.

1. Local validation passing:

$ paconn validate --api-def certified-connectors/MailSlurp/apiDefinition.swagger.json
> Swagger certification succeeded with warnings...

2. I have remove the offending paths that had bad schema responses
3. However, the /info/version and /info/contact/name do indeed exist. Is it possible your validation is mistaken?

[jackmahoney]

@vmanoharas am I missing something regarding the version an contact name you mentioned?