Inconsistent implementation of user `type` field

There is a type field on the user schema that isn't returning the correct assignment for bots created by an admin. The only time it seems to assign the type as bot is for the internal Rocket.Cat user.

It would be good for the type to be set as bot whenever the bot role is given, because by default, bots don't have permission query the role field through the API, their only way to determine bots from other users in a request would be the type field.

Here's an example API result from my local instance where I have the default admin and bot, plus another "Mock" user and "Bot" - showing the bot gets the "user" type.

[
	{
		"name": "Administrator",
		"username": "admin",
		"status": "away",
		"type": "user",
		"_id": "Ymuzcj8dhFZ2i7k89"
	},
	{
		"name": "Bot",
		"username": "bot",
		"status": "online",
		"type": "user",
		"_id": "TFGnsAWgwEMrhEYBq"
	},
	{
		"name": "Mock User",
		"username": "mock",
		"status": "online",
		"type": "user",
		"_id": "4Q76Aj9Tdbm4mM2WR"
	},
	{
		"name": "Rocket.Cat",
		"username": "rocket.cat",
		"status": "online",
		"type": "bot",
		"_id": "rocket.cat"
	}
]

Start by tracing the user schema's type assignment and the handling of the bot role, then reproduce the API response shown in the issue with an admin-created bot. Done means users granted the bot role return type "bot" through the API, while ordinary users continue to return type "user".