Build: Fix exceptions

[stsewd]

We were passing the path to the constructor,
but that argument is actually the message.

The message is already defined in the exception itself.

Fixes #10538

[humitos]

We were passing the path to the constructor, but that argument is actually the message.

What about checking the message= type is string in the initializer?

readthedocs.org/readthedocs/doc_builder/exceptions.py

Lines 9 to 19 in bbb200b

	class BuildBaseException(Exception):
	message = None
	status_code = None
	def __init__(self, message=None, **kwargs):
	self.status_code = kwargs.pop(
	'status_code',
	None,
	) or self.status_code or 1
	self.message = message or self.message or self.get_default_message()
	super().__init__(message, **kwargs)

Or, cast it into string?

I'm thinking about a way to avoid this issue since we've hit long time ago and it was hard to track. I remember talking to Anthony about this and we weren't able to figure it out what was happening.

[stsewd]

What about checking the message= type is string in the initializer? Or, cast it into string?

Do you mean raising an exception if the type is incorrect? I'm +1 on that instead of casting, since looks like most of the time, passing that argument to exceptions that have an already defined default message is a mistake.

[stsewd]

Didn't find any other exceptions where we were overriding the default message like this.