[tools/shoestring]: light rest implementation

[AnthonyLaw]

What was the issue?

• Implement light REST functionality into tools.

What's the fix?

• to set full API node in sai.ini config: features = API and lightApi = false.
• to set light rest node in sai.ini config: features = API and lightApi = true.
• Added full_api flag in node configuration to define setup full API node.
• Added a docker compose template for light setup.
• Implemtation all related light config in a shoestring.

Light rest is a subset of full API. I extracted the configuration and applied it to the condition check.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.23%. Comparing base (4afb34a) to head (ee91545).

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #1165      +/-   ##
==========================================
- Coverage   98.25%   98.23%   -0.02%     
==========================================
  Files         162      157       -5     
  Lines        6630     6501     -129     
  Branches      143      143              
==========================================
- Hits         6514     6386     -128     
+ Misses        116      115       -1     

Flag	Coverage Δ
explorer-rest	?
tools-shoestring	96.87% <100.00%> (+<0.01%)	⬆️

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

Files with missing lines	Coverage Δ
tools/shoestring/shoestring/commands/reset_data.py	100.00% <100.00%> (ø)
tools/shoestring/shoestring/commands/setup.py	100.00% <ø> (ø)
tools/shoestring/shoestring/commands/upgrade.py	100.00% <100.00%> (ø)
...s/shoestring/shoestring/healthagents/websockets.py	100.00% <100.00%> (ø)
tools/shoestring/shoestring/internal/Preparer.py	100.00% <100.00%> (ø)
...ing/shoestring/internal/ShoestringConfiguration.py	100.00% <100.00%> (ø)

... and 5 files with indirect coverage changes

[Wayonb]

looks good 👍🏾

have a few questions.

[AnthonyLaw]

I guess now that you added back the rest_cache folder then this is not needed? 🤔

I must understand wrongly, I thought you wanted to keep the rest_cache.
I will revert the change.

[Wayonb]

I guess now that you added back the rest_cache folder then this is not needed? 🤔

I must understand wrongly, I thought you wanted to keep the rest_cache. I will revert the change.

No, I meant since you added back the rest_cache, the below code can be moved back

		if NodeFeatures.API in self.config.node.features and self.config.node.api_https:
			directories.append(self.directories.https_proxy)

		if NodeFeatures.API in self.config.node.features:
			directories.append(self.directories.rest_cache)

=>

		if NodeFeatures.API in self.config.node.features:
			directories.append(self.directories.rest_cache)
			 if self.config.node.api_https:
			     directories.append(self.directories.https_proxy)
"

[Wayonb]

👍🏾