pjsip_config.xml: Fix omissions caused by wrong cherry-pick order

When cherry-picking geolocation prerequisites to the certified/18.9
branch, the commit that moved res_pjsip documentation to separate
XML files was cherry-picked after other that assumed it was
already there.  This caused a few configuration options to be
dropped from the XML and prevented res_stir_shaken and some
pjsip transports to fail to load.

Those entries are now in their correct spots in pjsip_config.xml.

A housekeeping change was also made to both pjsip_config.xml and
pjsip_manager.xml to add stylesheet and namespace info.

Change-Id: I0ea2eb191e006673f4fa3caafb2edbc92b3e1214

res/res_pjsip/pjsip_config.xml

@@ -1,6 +1,7 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE docs SYSTEM "appdocsxml.dtd">
-<docs>
+<?xml-stylesheet type="text/xsl" href="appdocsxml.xslt"?>
+<docs xmlns:xi="http://www.w3.org/2001/XInclude">
 	<configInfo name="res_pjsip" language="en_US">
 		<synopsis>SIP Resource using PJProject</synopsis>
 		<configFile name="pjsip.conf">
@@ -1423,6 +1424,13 @@
 						INVITEs, an Identity header will be added.</para>
 					</description>
 				</configOption>
+				<configOption name="stir_shaken_profile" default="">
+				        <synopsis>STIR/SHAKEN profile containing additional configuration options</synopsis>
+				        <description><para>
+				                A STIR/SHAKEN profile that is defined in stir_shaken.conf. Contains
+				                several options and rules used for STIR/SHAKEN.</para>
+				        </description>
+				</configOption>
 				<configOption name="allow_unauthenticated_options" default="no">
 					<synopsis>Skip authentication when receiving OPTIONS requests</synopsis>
 					<description><para>
@@ -1773,6 +1781,18 @@
 						in-progress calls.</para>
 					</description>
 				</configOption>
+				<configOption name="allow_wildcard_certs" default="false">
+					<synopsis>Allow use of wildcards in certificates (TLS ONLY)</synopsis>
+					<description>
+						<para>In combination with verify_server, when enabled allow use of wildcards,
+							i.e. '*.' in certs for common,and subject alt names of type DNS for TLS
+							transport types. Names must start with the wildcard. Partial wildcards, e.g.
+							'f*.example.com' and 'foo.*.com' are not allowed. As well, names only match
+							against a single level meaning '*.example.com' matches 'foo.example.com',
+							but not 'foo.bar.example.com'.
+						</para>
+					</description>
+				</configOption>
 				<configOption name="symmetric_transport" default="no">
 					<synopsis>Use the same transport for outgoing requests as incoming ones.</synopsis>
 					<description>

res/res_pjsip/pjsip_manager.xml

@@ -1,6 +1,7 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE docs SYSTEM "appdocsxml.dtd">
-<docs>
+<?xml-stylesheet type="text/xsl" href="appdocsxml.xslt"?>
+<docs xmlns:xi="http://www.w3.org/2001/XInclude">
 	<manager name="PJSIPQualify" language="en_US">
 		<synopsis>
 			Qualify a chan_pjsip endpoint.