### 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
#include "gdscript_parser.h"
#include "core/config/project_settings.h"
#include "core/io/file_access.h"
#include "core/io/resource_loader.h"
#include "core/math/math_defs.h"
#include "gdscript.h"
#include "scene/main/multiplayer_api.h"
#ifdef DEBUG_ENABLED
#include "core/os/os.h"
#include "core/string/string_builder.h"
#include "gdscript_warning.h"
#include "servers/text_server.h"
#endif 
#ifdef TOOLS_ENABLED
#include "editor/editor_settings.h"
#endif 
static HashMap<StringName, Variant::Type> builtin_types;
Variant::Type GDScriptParser::get_builtin_type(const StringName &p_type) {
	if (builtin_types.is_empty()) {
		for (int i = 1; i < Variant::VARIANT_MAX; i++) {
			builtin_types[Variant::get_type_name((Variant::Type)i)] = (Variant::Type)i;
		}
	}
	if (builtin_types.has(p_type)) {
		return builtin_types[p_type];
	}
	return Variant::VARIANT_MAX;
}
void GDScriptParser::cleanup() {