### Godot version

v4.0.stable.official [92bee43ad]

### System information

Steam OS Holo, Steam Deck

### Issue description

Using a `[br]` tag at the end of a line in a documentation comment adds an additional space at the beginning of the following line:

![image](https://user-images.githubusercontent.com/857660/236700815-c78a317f-cdf8-4f3c-8489-41f9559ffe6d.png)


### Steps to reproduce

The script below is what I used to generate the image above:

```gdscript
class_name Test
extends Node

## High-level description
##
## First line of detail.[br]
## Second line of detail.
```

Removing the space between `##` and `Second` doesn't change the output.

The only workaround I've found so far is to remove the linebreak after the `[br]` tag, but this makes the documentation comments harder to read in the editor:

```gdscript
class_name Test
extends Node

## High-level description
##
## First line of detail.[br]Second line of detail.
```

### Minimal reproduction project

N/A
if (!consume(GDScriptTokenizer::Token::IDENTIFIER, R"(Expected parameter name.)")) {
		return nullptr;
	}
	ParameterNode *parameter = alloc_node<ParameterNode>();
	parameter->identifier = parse_identifier();
	if (match(GDScriptTokenizer::Token::COLON)) {
		if (check((GDScriptTokenizer::Token::EQUAL))) {
			
			parameter->infer_datatype = true;
		} else {
			
			make_completion_context(COMPLETION_TYPE_NAME, parameter);
			parameter->datatype_specifier = parse_type();
		}
	}
	if (match(GDScriptTokenizer::Token::EQUAL)) {
		
		parameter->initializer = parse_expression(false);
	}
	complete_extents(parameter);
	return parameter;
}
GDScriptParser::SignalNode *GDScriptParser::parse_signal(bool p_is_static) {
	SignalNode *signal = alloc_node<SignalNode>();
	if (!consume(GDScriptTokenizer::Token::IDENTIFIER, R"(Expected signal name after "signal".)")) {
		complete_extents(signal);
		return nullptr;
	}
	signal->identifier = parse_identifier();
	if (check(GDScriptTokenizer::Token::PARENTHESIS_OPEN)) {