fix(direct-access): save context not present if direct access enabled

[omairvaiyani]

Related PR introduced a new feature but does not work with experimental Direct Access which uses ParseServerRESTController.

Proposed change just adds context into data as expected by RestWrite

Open discussion for feature with other issues

[codecov]

Codecov Report

Merging #6764 into master will decrease coverage by 0.58%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6764      +/-   ##
==========================================
- Coverage   93.90%   93.32%   -0.59%     
==========================================
  Files         169      169              
  Lines       12197    12197              
==========================================
- Hits        11454    11383      -71     
- Misses        743      814      +71     

Impacted Files	Coverage Δ
...dapters/Cache/RedisCacheAdapter/KeyPromiseQueue.js	0.00% <0.00%> (-95.46%)	⬇️
src/Adapters/Cache/RedisCacheAdapter/index.js	12.50% <0.00%> (-82.15%)	⬇️
src/Routers/PushRouter.js	93.10% <0.00%> (-3.45%)	⬇️
src/Adapters/Storage/Mongo/MongoStorageAdapter.js	92.87% <0.00%> (-0.67%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4f7fd17...c0508e9. Read the comment docs.

[dplewis]

Can you add a test case? Looks good!

[dplewis]

@yog27ray Shouldn't this be fix via #6666 now that you moved context to the middleware?

[dplewis]

@omairvaiyani I'm going to add a test case to cover direct access. This has already been fixed via
https://github.com/parse-community/parse-server/pull/6666/files#diff-698500347c579cf381cfce33fb74e2ff

[omairvaiyani]

@dplewis thanks for that! My apologies for the uncertainty around the fix. We've been settled on parse-server v3~ since the GraphQL Relay change so my patches are hazy!