convert to dynamic config; return boolean, numeric and string responses (FF-860)

[leoromanovsky]

Fixes: #issue

Motivation and Context

Adds support for typed response functions.

Description

• enable strict null checks
• Keeps getAssignment(...): string
• Adds getStringAssignment, getBoolAssignment, getNumericAssignment, getJSONAssignment
• Created EppoValue class

How has this been tested?

unit tests

[leoromanovsky]

the pre and post assignment events caused a bunch of duplicate code in these handlers

[agamkrbit]

👍

[agamkrbit]

@leoromanovsky Can we test it with the updated test data from the GitHub Repository?

[leoromanovsky]

Thanks Agam for the suggestion to add the new test cases the latest ones brought up a bug that I corrected.

I also had a hard time getting the new test-data command working as it is written in the java repo; seemed like a race condition was happening where git clone wasn't getting waited on and the script crashing trying to copy a json file. I've fixed it with the version as written:

testDataDir := test/data/
tempDir := ${testDataDir}temp/
gitDataDir := ${tempDir}sdk-test-data/
branchName := main
githubRepoLink := https://github.com/Eppo-exp/sdk-test-data.git
repoName := sdk-test-data
.PHONY: test-data
test-data: 
	rm -rf $(testDataDir)
	mkdir -p $(tempDir)
	git clone -b ${branchName} --depth 1 --single-branch ${githubRepoLink} ${gitDataDir}
	cp ${gitDataDir}rac-experiments-v3.json ${testDataDir}
	cp -r ${gitDataDir}assignment-v2 ${testDataDir}
	rm -rf ${tempDir}

👉 Last bit of "clean up" I'd like to do here is try to unify the IValue and EppoValue types - will do a bit of research to see what's possible with json deserialization.

https://medium.com/@aems/one-mans-struggle-with-typescript-class-serialization-478d4bbb5826

[aarsilv]

🔥

[aarsilv]

minor but with short-circuiting and I think we could simplify this to return ba && EppoValue.Bool(ba).

> v = null
null
> v && Bool(v)
null
> v = true
true
> v && Boolean(v)
true

[aarsilv]

🙌