257 user model refactor the config handling

[michalkrzem]

Your checklist for this pull request

• I've read the contributing guideline.
• I've tested my changes by building and running mquery, and testing changed functionality (if applicable)
• I've added automated tests for my change (if applicable, optional)
• I've updated documentation to reflect my change (if applicable)

What is the current behaviour?
db.get_mquery_config_key("default_role) when called returns different types

What is the new behaviour?
I created UserModelConfig with properties like auth_default_roles, openid_client_id, query_allow_slow etc. and now i call db.config.default_role

Test plan

Closing issues

fixes #257

[msm-cert]

Suggested change

	auth_enabled = self.db.get_mquery_config_key("auth_enabled")
	if not auth_enabled or auth_enabled == "false":
	return False
	return True
	return self.db.get_mquery_config_key("auth_enabled") == "true"

Tiny chance in behaviour, but consistent with query_allow_slow (and works the same way for "true" and "false")

[michalkrzem]

brilliant :)

[msm-cert]

Suggested change

	def openid_client_id(self) -> str:
	def openid_client_id(self) -> str | None:

[msm-cert]

(if this causes type errors somewhere else, callers should be fixed to handle the situation where this is null)

[michalkrzem]

Done

[msm-cert]

Suggested change

	def openid_url(self) -> str:
	def openid_url(self) -> str | None:

[michalkrzem]

Done

[msm-cert]

I suspect this will cause issues on the frontend (but you can check). Unfortunately, you should probably cast to str when creating ServerSchema.