Although, password file is checked during config validation, sth may have changed the
file content in the short period of time between validation and DB client initialization,
hence exiting in case of an error

* remove some spaces
* return item.Name() instead of map key
* re-order router log output

The location where the actual items should reside is in the store, while
only references are being returned when attempting to access an item.

Fore more information see https://go.dev/blog/maps#concurrency

For now it's just ephemeral.

Instead of disabling the timeout (-1), it's set to 1 ms for all requests
in the state paths test. Otherwise race condistion may occur. Symptoms include
incorrect state name, because it may have been read before it's fully written
to the store.