ParallelQueryExecutionContextBase breaks use of abortSignal

[jay-most]

@azure/cosmos:
3.14.1:
Describe the bug
If an abortSignal object is passed within the FeedOptions object of a query AND
a query rewrite response is initially received by the SDK, an exception is thrown:

userSignal.addEventListener is not a function
The issue is within the function ParallelQueryExecutionContextBase._createTargetPartitionQueryExecutionContext which is attempting to make a deep copy of the query options using JSON.parse(JSON.stringify(...)). This will copy object data but will not copy the abortSignal object member functions which are required to add event listeners for abort triggers.

I recommend the following change for line 474 of azure-sdk-for-js/sdk/cosmosdb/cosmos/src/queryExecutionContext/parallelQueryExecutionContextBase.ts

•    const options = JSON.parse(JSON.stringify(this.options));
  

•    const options = Object.assign(Object.create(Object.getPrototypeOf(this.options)), this.options);
  

To Reproduce
Steps to reproduce the behavior:

Query a container for items options.abortSignal defined and a SqlQuerySpec that will trigger a query rewrite.
const abortController = new AbortController();
const querySpec: SqlQuerySpec = {
query: "SELECT MAX(c._ts) as _ts, c.someAttrib FROM c WHERE IS_DEFINED(c.someAttrib) GROUP BY c.someAttrib",
parameters: [
]
};
const options: FeedOptions = {
abortSignal: abortController.signal
};
const iterator = container.items.query(querySpec, options);
Expected behavior
No exception thrown.

[kushagraThapar]

Overall looks good to me, thanks @jay-most

[ghost]

Hi @jay-most. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[ghost]

Hi @jay-most. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing "/reopen" if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the "no-recent-activity" label; otherwise, this is likely to be closed again with the next cleanup pass.

[jay-most]

@kushagraThapar