Fix async behavior of the NCCO record action

[erickskrauch]

Description

As described in the documentation, the record action is asynchronous by default, unless it has endOnSilence, timeOut or endOnKey params. The current implementation of the Record action in this library provides no way to not specify that param.

Motivation and Context

We need to achieve an async behavior of the record action.

How Has This Been Tested?

We have made calls with those changes.

Example Output or Screenshots (if appropriate):

Call CON-b4cc19a0-ffd7-4e44-80ec-2d7ecf05c44c.

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] I have read the CONTRIBUTING document.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

[SecondeJK]

This can be merged when it is time to release 5.0.0 (as although it's a fix, it's a semver breaking change in line with how the Record NCCO works currently)

[SecondeJK]

I've just picked up an internal ticket and fixed this in a different PR, although the solution seems to be much the same. Thanks for opening it though! #493