These methods either
- only wrap QSettings values (so there's no added security gained
by not exposing them -- it's currently easily possible to achieve
the same results via direct QSettings manipulation)
OR
- are required to allow fully automated QGIS deployment/startup
scripts which rely on auth manager functionality