ARI: Added paths to get and set multiple channel variables.

[bkford]

Two new paths exist for ARI to get and set multiple channel variables at
the same time. This is done via GET and POST like the single get and set
variable equivalents. Leading and trailing whitespace will be stripped
from the variable names for both paths. When setting variables, the
values will be read as-is, whitespace included. GET takes in a single
string with comma-separated values, while POST takes in a dictionary of
key value pairs. The code follows the same paths as when setting
multiple variables when originating a channel via ARI.

UserNote: Added new ARI paths for getting and setting multiple channel
variables at a time. For GET, this takes in a single string of
comma-separated variable names, while POST takes in a dictionary of key
value pairs. The behavior is the same as passing in variables when
originating a channel.

[bkford]

cherry-pick-to: 23
cherry-pick-to: 22
cherry-pick-to: 20

[github-actions]

Workflow Check completed successfully

[github-actions]

Workflow Check completed successfully

[gtjoseph]

In the commit message, I don't understand what the following means...

You can also use getChannelVars and setChannelVars in your applications.

[bkford]

NOTE
One concern I have is the locking, so extra eyes on that would be greatly appreciated. The main concerns are:

1. When setting multiple variables, ast_set_variables is called and locks the channel. It eventually gets to pbx_builtin_setvar_helper, which ALSO locks the channel. Originating a channel also does this.
2. When setting a single variable (the original, existing path), it calls a different function: stasis_app_control_set_channel_var. This does NOT lock the channel before calling, but it ALSO eventually gets to pbx_builtin_setvar_helper.
3. In the original, existing get variable function, it makes a note of not locking when reading from the channel due to potential locking issues, especially with autoservice dialplan functions. It may not have anything to do with a write, but it's a concern I had.

[github-actions]

Workflow Check completed successfully

[github-actions]

Workflow Check completed successfully

Resolved

Resolved

[github-actions]

Workflow Check completed successfully

[gtjoseph]

LGTM pending the addition of the testsuite test.
When that's ready, don't forget to update this PR with a testsuite-test-pr: nnnn comment so the two PRs can be tested together.

Resolved

[bkford]

testsuite-test-pr: 131

[github-actions]

Workflow Check completed successfully

[github-actions]

Workflow Check failed
master-app_dial: FAILED TEST: apps/queues/transfer/caller_attended
master-ari2: FAILED TEST: rest_api/channels/channel_variables/get_set_multiple