In Core 26.0, if you specify a conf file with `-conf=/somewhere/bitcoin.conf`, bitcoind refuses to start, if you also have another `bitcoin.conf` in your datadir, and issues a warning, unless you also have another option set : `allowignoredconf=1`. This seems like overengineering, how likely is it that I would explicitly set the conf file location and not want to use it?