sqlite3: Vendor import of sqlite3 3.43.1

Release notes at https://www.sqlite.org/releaselog/3_43_1.html.

Obtained from: https://www.sqlite.org/2023/sqlite-autoconf-3430100.tar.gz

MFC after: 2 weeks

Merge commit 'fa2bb1440e13602676feec708ac7a9a3bb5ce5c8' into main

MFV 364467:

Update sqlite to 3.33.0 (3330000).

Release announcement at https://www.sqlite.org/releaselog/3_33_0.html.

MFC after: 1 month

MFV r342175:

Update sqlite3-3.23.1 --> sqlite3-3.26.0 (3260000)

MFC after: 3 days
Security: https://blade.tencent.com/magellan/index_en.html
No known CVE was apparently registered.

Update private sqlite from sqlite3-3.20.0 to sqlite3-3.23.1

MFV r304732.

Update from sqlite3-3.12.1 (3120100) to sqlite3-3.14.1 (3140100).

This commit addresses the tmpdir selection vulnerability fixed in
sqlite3-1.13.0. See VuXML entry 546deeea-3fc6-11e6-a671-60a44ce6887b.

Security: VuXML 546deeea-3fc6-11e6-a671-60a44ce6887b
Security: CVE-2016-6153

Import sqlite3 3.12.1

Update the private sqlite3 from 3.8.9 to 3.8.11.1 (used by svnlite and
kerberos)

Introduce svnlite so that we can check out our source code again.

This is actually a fully functional build except:
* All internal shared libraries are static linked to make sure there
is no interference with ports (and to reduce build time).
* It does not have the python/perl/etc plugin or API support.
* By default, it installs as "svnlite" rather than "svn".
* If WITH_SVN added in make.conf, you get "svn".
* If WITHOUT_SVNLITE is in make.conf, this is completely disabled.

To be absolutely clear, this is not intended for any use other than
checking out freebsd source and committing, like we once did with cvs.

It should be usable for small scale local repositories that don't
need the python/perl plugin architecture.