fix: correct assertions for shorthand targeting

[toddbaert]

When I first wrote these assertions, I had incorrectly setup the cuke bindings in the JS repo where I tested it; I was setting the targeting key to "[email protected]" (including the quotes!!!) which obviously resulted in a different assignment. Then when I started implementing these tests in other repos, nothing worked 😅

These are the actual correct responses, which you can test in flagd:

curl -X POST "http://localhost:8013/flagd.evaluation.v1.Service/ResolveString"       -d '{"flagKey":"fractional-flag-shorthand","context":{"targetingKey":"[email protected]"}}' -H "Content-Type: application/json"

// {"value":"tails","reason":"TARGETING_MATCH","variant":"tails","metadata":{}}

curl -X POST "http://localhost:8013/flagd.evaluation.v1.Service/ResolveString"       -d '{"flagKey":"fractional-flag-shorthand","context":{"targetingKey":"[email protected]"}}' -H "Content-Type: application/json"

// {"value":"heads","reason":"TARGETING_MATCH","variant":"heads","metadata":{}}