Avoid warning "no explicit project encoding"

Eclipse 2022-06 raises that warning for each project without explicit
encoding. Even though we have an Oomph setup, there is no harm in adding
the setting to avoid the warning.

Signed-off-by: Michael Keppler <Michael.Keppler@gmx.de>
Change-Id: I254ac4ee69a23becc27b5b9db45e60666218f981

org.eclipse.egit.github.core.tests/.settings/org.eclipse.core.resources.prefs

diff --git a/org.eclipse.egit.github.core.tests/.settings/org.eclipse.core.resources.prefs b/org.eclipse.egit.github.core.tests/.settings/org.eclipse.core.resources.prefs
new file mode 100644
index 0000000..99f26c0
--- /dev/null
+++ b/org.eclipse.egit.github.core.tests/.settings/org.eclipse.core.resources.prefs
@@ -0,0 +1,2 @@
+eclipse.preferences.version=1
+encoding/<project>=UTF-8

org.eclipse.egit.github.core/.settings/org.eclipse.core.resources.prefs

diff --git a/org.eclipse.egit.github.core/.settings/org.eclipse.core.resources.prefs b/org.eclipse.egit.github.core/.settings/org.eclipse.core.resources.prefs
new file mode 100644
index 0000000..99f26c0
--- /dev/null
+++ b/org.eclipse.egit.github.core/.settings/org.eclipse.core.resources.prefs
@@ -0,0 +1,2 @@
+eclipse.preferences.version=1
+encoding/<project>=UTF-8