### 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 (locals_indices.has(p_name)) {
		return true;
	}
	if (parent_block != nullptr) {
		return parent_block->has_local(p_name);
	}
	return false;
}
const GDScriptParser::SuiteNode::Local &GDScriptParser::SuiteNode::get_local(const StringName &p_name) const {
	if (locals_indices.has(p_name)) {
		return locals[locals_indices[p_name]];
	}
	if (parent_block != nullptr) {
		return parent_block->get_local(p_name);
	}
	return empty;
}
bool GDScriptParser::AnnotationNode::apply(GDScriptParser *p_this, Node *p_target) {
	if (is_applied) {
		return true;
	}
	is_applied = true;
	return (p_this->*(p_this->valid_annotations[name].apply))(this, p_target);
}
bool GDScriptParser::AnnotationNode::applies_to(uint32_t p_target_kinds) const {
	return (info->target_kind & p_target_kinds) > 0;
}
bool GDScriptParser::validate_annotation_arguments(AnnotationNode *p_annotation) {