cli-test(feat): Added datastore CLI commands

[cchensh]

Summary

This PR adds basic datastore CLI commands for e2e test, it includes datastore get/put/query/delete

Requirements (place an x in each [ ])

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[cchensh]

Here I'm using general string for datastore commands to make it easier than pre-define attributes such as datastore, item, and expression, etc

[filmaj]

I feel like this will make it easy to make mistakes. I think we should model these just like we model the actual methods:

• apps.datastore.get method needs datastore string and id string
• apps.datastore.query method needs datastore string, and its optional arguments, etc.

[cchensh]

It makes sense, I'd say for get method, id is not a must as it's defined in the manifest as primary key. I'd like to change by adding the datastore as the new argument here.

Edit: my bad the id is always presented for get and delete command.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.74%. Comparing base (0861218) to head (2562383).
Report is 19 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2041      +/-   ##
==========================================
- Coverage   92.51%   91.74%   -0.77%     
==========================================
  Files          37       38       +1     
  Lines        9981    10081     +100     
  Branches      631      631              
==========================================
+ Hits         9234     9249      +15     
- Misses        747      820      +73     
- Partials        0       12      +12     

Flag	Coverage Δ
cli-hooks	95.23% <ø> (ø)
cli-test	95.69% <100.00%> (-0.32%)	⬇️
oauth	77.39% <ø> (-4.13%)	⬇️
socket-mode	58.22% <ø> (-0.86%)	⬇️
web-api	96.89% <ø> (-0.40%)	⬇️
webhook	96.65% <ø> (-0.42%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

[filmaj]

I think we should model the API arguments as they are documented on our public docs 😞 sorry, I know that's annoying, but if we accept these JSON-payloads-as-strings, it would require a breaking change / major new version to change it to make it more accurate. I think the chance of making a typo with the string-based arguments is too high.

[filmaj]

I feel like this will make it easy to make mistakes. I think we should model these just like we model the actual methods:

• apps.datastore.get method needs datastore string and id string
• apps.datastore.query method needs datastore string, and its optional arguments, etc.