doc: Do s/int/integer/ to describe the type of some GUC parameters

Three parameters have been using "int" rather than "integer" to describe
their type:
auth_delay.milliseconds
max_logical_replication_workers
pg_prewarm.autoprewarm_interval

This is inconsistent with any other integer GUCs listed in the docs
(148, as far as I can see).

Author: Peter Smith
Discussion: https://postgr.es/m/CAHut+Pv6X5T-veN2abUDUvBxZm+SSm-9otfi3LZPGyOc6u6hiA@mail.gmail.com

Author: michaelpq

doc/src/sgml/auth-delay.sgml

@@ -27,7 +27,7 @@
   <variablelist>
    <varlistentry>
     <term>
-     <varname>auth_delay.milliseconds</varname> (<type>int</type>)
+     <varname>auth_delay.milliseconds</varname> (<type>integer</type>)
      <indexterm>
       <primary><varname>auth_delay.milliseconds</varname> configuration parameter</primary>
      </indexterm>

doc/src/sgml/config.sgml

@@ -4922,7 +4922,7 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
      <variablelist>
 
      <varlistentry id="guc-max-logical-replication-workers" xreflabel="max_logical_replication_workers">
-      <term><varname>max_logical_replication_workers</varname> (<type>int</type>)
+      <term><varname>max_logical_replication_workers</varname> (<type>integer</type>)
       <indexterm>
        <primary><varname>max_logical_replication_workers</varname> configuration parameter</primary>
       </indexterm>

doc/src/sgml/pgprewarm.sgml

@@ -107,7 +107,7 @@ autoprewarm_dump_now() RETURNS int8
   <variablelist>
    <varlistentry>
    <term>
-     <varname>pg_prewarm.autoprewarm_interval</varname> (<type>int</type>)
+     <varname>pg_prewarm.autoprewarm_interval</varname> (<type>integer</type>)
      <indexterm>
       <primary><varname>pg_prewarm.autoprewarm_interval</varname> configuration parameter</primary>
      </indexterm>