[FEATURE] Add Flag and Gherkin Assertions To Test Missing and `null` `defaultValue`

[toddbaert]

As outlined here, we want to support the defaultValue being optional. This will allow users to omit this field, which will indicate that flagd providers should revert to the code default for the flag in question, if targeting is not defined or falls through.

We need to enhance the gherkin suite to test this use-case.

Steps

• add flags with null and undefined defaultValue and no targeting
• add flags with null and undefined defaultValue and defined targeting
• add Gherkin assertions testing that when targeting falls through or is undefined, the supplied code default is used, and the FLAG_NOT_FOUND error code is set

[Rahul-Baradol]

Could you assign this to me :)

[toddbaert]

@Rahul-Baradol how are you progressing with this? I see you also have the Java provider implementation assigned to you here. Are you working on both in conjunction?

Especially the gherkin can be tricky if you're not familiar with it. Can I help it any way?

[Rahul-Baradol]

Haven't started this yet.

Will ping you if I get stuck somewhere.
Will first start with java provider if that sounds cool.

[toddbaert]

Haven't started this yet.

Will ping you if I get stuck somewhere. Will first start with java provider if that sounds cool.

Yes, that's fine with me. In fact, if you want, you can do the Java provider, and then I can do this issue to validate your work with updated e2e tests.

[Rahul-Baradol]

Yeah that works for me :)
You can go ahead with this, I will be working on java provider!