Add Records+JsonAnySetter workarounds shared in #3439, as test cases.

[yihtserns]

2 out of 3 workarounds no longer work, but I still added them anyway for awareness. UPDATE: Removed them.

[cowtowncoder]

Ok, as per my note, I don't like the idea of test that verifies incorrect behavior.
Tests should only test correct, expected behavior: but to avoid CI failure blocking builds, such failing tests should be in test class(es) under src/test/.../failing.

[yihtserns]

Should I just remove the test cases for workarounds that are no longer working? Putting them in src/test/.../failing seems inappropriate since I wouldn't expect them to pass in the future, ever.

[cowtowncoder]

Should I just remove the test cases for workarounds that are no longer working? Putting them in src/test/.../failing seems inappropriate since I wouldn't expect them to pass in the future, ever.

Ah. Yes, if that's the case, let's just remove them. I was assuming they were to be resolved in future.

[yihtserns]

Turns out there WAS test created for Records+JsonAnySetter, but the scenario is only when @JsonAnySetter is on a constructor parameter directly, not on a Record component: https://github.com/FasterXML/jackson-databind/blob/2.18/src/test-jdk17/java/com/fasterxml/jackson/databind/records/RecordCreatorWithAnySetter562Test.java

That explains why it didn't catch the regression caused by #4627.

[yihtserns]

Now that I know RecordCreatorWithAnySetter562Test.java exists, I'll rewrite-move my tests into that class.

[yihtserns]

Seems like this has become a duplicate of fb82b5b.

Closing.