feat: showcase dynamic derived data with SDK

[kschiew]

Working draft for testing TypeScript SDK rules() API.

Deploy Notes

** Environment variables **:

• RULES_ENGINE_DEV_ENDPOINT: Rules Engine local endpoint, eg "http://localhost:3001/api/rules/eval"
• SGID_RULE_IDS: A space-separated string consisting of rule ID's passed into Rules API call, eg "ISOGPOFFICER-53270fce ISOGPOFFICER-aed06721"

[kwajiehao]

What's the rationale for rule names to be defined as a separate variable as opposed to an argument to the sgID client?

[kschiew]

I was mirroring how scopes work - RP's have the options to pass in different sets of scopes for every complete sgID flow. Let's say we pass in rules as an argument to the sgID client (eg. <some_rule_that_depends_on_pocdex.public_officer_employments>), and if RP did not pass in pocdex.public_officer_employments in authUrl, the Rules API call would fail because RP has not obtained consent for the underlying referenced field.

Besides, I think having consistency in how we handle scopes and rules would be good DX.

p/s: We are using rule ID's instead of rule names to identify rules now because of Rules Engine design changes.