[invocation-overhead] git ignore generated source files.

[jpobst]

Building the Java.Interop.sln solution always produces some generated files that git wants to try to commit:

Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: tests/invocation-overhead/jni.cs
Untracked files:
(use "git add <file>..." to include in what will be committed)
tests/invocation-overhead/jni-api.h
tests/invocation-overhead/jni.c

Ignore these files with .gitignore.

Note that the first time we generate jni.cs we need to manually add it to @(Compile) because the wildcard expansion has already executed at that point. Additional times the file gets regenerated we use KeepDuplicates='false' to prevent a duplicate @(Compile) file warning.

[jonpryor]

We should probably instead addtests/invocation-overhead/jni-api.h and tests/invocation-overhead/jni.c, and update tests/invocation-overhead/jni.cs, as these are useful ways to see what build-tools/jnienv-gen output is, without needing to build the repo itself and look at e.g. src/Java.Interop/obj/Debug/net7.0/JniEnvironment.g.cs or src/java-interop/obj/Debug-net7.0/jni.c.

For example, consider 0f1efeb, which updated jnienv-gen, and also included updates to tests/invocation-overhead/jni.cs. This made code review easier -- at least I'd like to think so -- because the changes introduced to jnienv-gen were visible in the same PR as changes to jni.cs.

[jpobst]

Sounds good to me. This solution also fulfills my desire of appeasing git. 😁

I'll update this PR to do this instead.

[jpobst]

Superseded by #1175.