fix: test: Handle example3.db being modified in upforwd system test

The zone file for example3 (ns1/example3.db) can be modified in the
upforwd test as example3 is updated as part of the test.  Whether
the zone is written out or not by the end of the test is timing
dependent.  Rename ns1/example3.db to ns1/example3.db.in and copy it to
ns1/example3.db in setup so we don't trigger post test changes checks.

Closes #5180

Merge branch '5180-create-example3-in-setup' into 'main'

See merge request isc-projects/bind9!10160

bin/tests/system/upforwd/setup.sh

@@ -14,6 +14,7 @@
 . ../conf.sh
 
 cp -f ns1/example1.db ns1/example.db
+cp -f ns1/example3.db.in ns1/example3.db
 cp -f ns3/noprimary.db ns3/noprimary1.db
 
 copy_setports ns1/named.conf.in ns1/named.conf

bin/tests/system/upforwd/tests_sh_upforwd.py

@@ -26,6 +26,7 @@ pytestmark = pytest.mark.extra_artifacts(
         "ns1/example.db",
         "ns1/example2-toomanykeys.db",
         "ns1/example2.db",
+        "ns1/example3.db",
         "ns3/dnstap.conf",
         "ns3/dnstap.out",
         "ns3/noprimary1.db",