### 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
advance();
			result = parse_match();
			break;
		case GDScriptTokenizer::Token::BREAK:
			advance();
			result = parse_break();
			break;
		case GDScriptTokenizer::Token::CONTINUE:
			advance();
			result = parse_continue();
			break;
		case GDScriptTokenizer::Token::RETURN: {
			advance();
			ReturnNode *n_return = alloc_node<ReturnNode>();
			if (!is_statement_end()) {
				if (current_function && (current_function->identifier->name == GDScriptLanguage::get_singleton()->strings._init || current_function->identifier->name == GDScriptLanguage::get_singleton()->strings._static_init)) {
					push_error(R"(Constructor cannot return a value.)");
				}
				n_return->return_value = parse_expression(false);
			} else if (in_lambda && !is_statement_end_token()) {
				
				
				n_return->return_value = parse_expression(false);
			}
			complete_extents(n_return);
			result = n_return;
			current_suite->has_return = true;
			end_statement("return statement");
			break;
		}