process: Backfill missing Version headers

…for BIPs that have a Changelog section that mentions a version.
BIP 1 and BIP 340 have Changelog sections, but do not define versions.

bip-0003.md

@@ -8,6 +8,7 @@
   License: BSD-2-Clause
   Discussion: https://github.com/murchandamus/bips/pull/2
               https://gnusha.org/pi/bitcoindev/59fa94cea6f70e02b1ce0da07ae230670730171c.camel@timruffing.de/#t
+  Version: 1.4.0
   Requires: 123
   Replaces: 2
 ```

bip-0077.md

@@ -12,6 +12,7 @@
   Discussion: https://github.com/bitcoin/bips/pull/1483
               https://gnusha.org/pi/bitcoindev/7B11AE34-27A7-46ED-95BF-66CA13BA26F3@ngould.dev/#t
               https://gnusha.org/pi/bitcoindev/3C0A6E4C-444E-4E75-829C-1A21D8EE40E0@ngould.dev/#t
+  Version: 0.2.0
   Requires: 21, 78, 173, 174
 ```
 

bip-0085.mediawiki

@@ -8,6 +8,7 @@
   Type: Informational
   Assigned: 2020-03-20
   License: BSD-2-Clause OR OPUBL-1.0
+  Version: 2.0.0
 </pre>
 
 ==Abstract==

bip-0155.mediawiki

@@ -7,6 +7,7 @@
   Type: Specification
   Assigned: 2019-02-27
   License: BSD-2-Clause
+  Version: 2.0.0
 </pre>
 
 ==Introduction==

bip-0327.mediawiki

@@ -10,6 +10,7 @@
   License: BSD-3-Clause
   Discussion: 2022-04-05: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020198.html [bitcoin-dev] MuSig2 BIP
               2022-10-11: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-October/021000.html [bitcoin-dev] MuSig2 BIP
+  Version: 1.0.3
 </pre>
 
 == Introduction ==
@@ -773,7 +774,7 @@ A scheme very similar to MuSig2 and with two-point nonces was independently prov
 This document proposes a standard for the MuSig2 multi-signature scheme that is compatible with [https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki BIP340].
 MuSig2 is ''not'' compatible with ECDSA signatures traditionally used in Bitcoin.
 
-== Change Log ==
+== Changelog ==
 
 To help implementers understand updates to this document, we attach a version number that resembles ''semantic versioning'' (<code>MAJOR.MINOR.PATCH</code>).
 The <code>MAJOR</code> version is incremented if changes to the BIP are introduced that are incompatible with prior versions.

bip-0352.mediawiki

@@ -12,6 +12,7 @@
               2022-03-28: https://gnusha.org/pi/bitcoindev/CAPv7TjbXm953U2h+-12MfJ24YqOM5Kcq77_xFTjVK+R2nf-nYg@mail.gmail.com/ [bitcoin-dev] Silent Payments – Non-interactive private payments with no on-chain overhead
               2022-10-11: https://gnusha.org/pi/bitcoindev/P_21MLHGJicZ-hkbC4DGu86c5BtNKiH8spY4TOw5FJsfimdi_6VyHzU_y-s1mZsOcC2FA3EW_6w6W5qfV9dRK_7AvTAxDlwVfU-yhWZPEuo=@protonmail.com/ [bitcoin-dev] Silent Payment v4 (coinjoin support added)
               2023-08-04: https://gnusha.org/pi/bitcoindev/ZM03twumu88V2NFH@petertodd.org/ [bitcoin-dev] BIP-352 Silent Payments addresses should have an expiration time
+  Version: 1.0.2
 </pre>
 
 == Introduction ==
@@ -480,7 +481,7 @@ A malicious notification could potentially cause the following issues:
 
 Wallet designers can choose which tradeoffs they find appropriate. For example, a wallet could check the block filter to at least probabilistically confirm the likely existence of the UTXO, thus efficiently cutting down on spam. The payment could then be marked as unconfirmed until a scan is performed and the existence of the UTXO in accordance to the silent payment specification is verified.
 
-== Change Log ==
+== Changelog ==
 
 To help implementers understand updates to this document, we attach a version number that resembles ''semantic versioning'' (<code>MAJOR.MINOR.PATCH</code>).
 The <code>MAJOR</code> version is incremented if changes to the BIP are introduced that are incompatible with prior versions.

bip-0374.mediawiki

@@ -11,6 +11,7 @@
   License: BSD-2-Clause
   Discussion: https://gist.github.com/andrewtoth/df97c3260cc8d12f09d3855ee61322ea
               https://groups.google.com/g/bitcoindev/c/MezoKV5md7s
+  Version: 0.2.0
 </pre>
 
 == Introduction ==