Only include fee 1.0 extension in nonprod envs (#2927)

We need to have this enabled in sandbox, but we wish to wait to enable
it for production to make sure that the implementation is correct and
that clients can use it.

Soon we'll want to do something similar (but the opposite) with the old
fee extensions, where we **only** serve them in production (or maybe
unit test as well). That will allow us to pass the RST tests that depend
on only having the fee extension 1.0.

core/src/test/resources/google/registry/flows/greeting.xml

@@ -15,6 +15,7 @@
         <extURI>urn:ietf:params:xml:ns:fee-0.6</extURI>
         <extURI>urn:ietf:params:xml:ns:fee-0.11</extURI>
         <extURI>urn:ietf:params:xml:ns:fee-0.12</extURI>
+        <extURI>urn:ietf:params:xml:ns:epp:fee-1.0</extURI>
       </svcExtension>
     </svcMenu>
     <dcp>

core/src/test/resources/google/registry/flows/session/greeting.xml

@@ -15,6 +15,7 @@
         <extURI>urn:ietf:params:xml:ns:fee-0.6</extURI>
         <extURI>urn:ietf:params:xml:ns:fee-0.11</extURI>
         <extURI>urn:ietf:params:xml:ns:fee-0.12</extURI>
+        <extURI>urn:ietf:params:xml:ns:epp:fee-1.0</extURI>
       </svcExtension>
     </svcMenu>
     <dcp>