Add skip meeting link generation for appointments

[jasonchucoconut]

Description

This pull request adds a new appointment filter to skip the meeting link generation for appointments that are done over a video call. This will allow the user to create an appointment that is to be done via video call to skip the meeting link generation at the moment of creation.

Motivation and context

The change is required when we are experiencing issues with the video platform that is blocking our appointment creation. We want the ability to bypass the video platform issue so we can let users create appointments. Video links can be generated at a later time when the issue has been resolved.

How has this been tested?

I have included two new tests to the set of appointment tests. They are focused on testing the new appointment filter withoutMeetingLink. The test cases are:

• Using the withoutMeetingLink without any arguments. The default value of the parameter is true.
• Using the withoutMeetingLink with a single argument value of false.

I have also updated two tests:

• "Can book an appointment with all available parameters".
  • Added the skip_meeting_link_generation property to the meta parameters.
• "Can reschedule an appointment with all available parameters".
  • Added the skip_meeting_link_generation property to the meta parameters.

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• 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 change)

Checklist:

Go over all the following points, and put an x in all the boxes that apply.

Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.

• I have read the CONTRIBUTING document.
• My pull request addresses exactly one patch/feature.
• I have created a branch for this patch/feature.
• Each individual commit in the pull request is meaningful.
• I have added tests to cover my changes.
• If my change requires a change to the documentation, I have updated it accordingly.

If you're unsure about any of these, don't hesitate to ask. We're here to help!