private static class field naming-issue when using Object.freeze()

### non-private field :+1:
```js
/**
* Holding builtin toHtml variants.
* @property {toHtml} classic - designed for {@link TaxiOptions}.data type of string[].
*/
static ToHtml = Object.freeze({
classic: (entry) => {
return `

`;
},
});
```
returns this documentation: (within the class scope)

### private field 👎🏼
where as this code (which is also within said class scope)
```js
/**
*
* Default TaxiOptions, to be used incase of none given.
* @property {*} data - ["Volkwagen", "Mercedes", "Daimler"]
* @property {query} query - {@link #taxiquery}
*/
static #TaxiOptionsDefaults = Object.freeze({
data: ["Volkwagen", "Mercedes", "Daimler"],
query: Taxi.Query.strict,
toHtml: Taxi.ToHtml.classic,
minChar: 1,
showWarnings: true,
});
```
Turns up below the class, as the following.

### I tried:
giving a `* @name ANYTHING_BUT_FREEZE` to the latter documentation, which didnt work.
and that is about it, i really like documentation.js but I don't know how to fix it apart from making it public which I'm not a fan of, since they needn't be public.

* What version of documentation.js are you using?: 13.1.1
* How are you running documentation.js (on the CLI, Node.js API, Grunt, other?): via npm(node.js) global install without sudo(not that that would make a difference)

any help would be appreciated, also if it means I need to change my code to something else, as long as it's not going to be public :D

Riproduci il problema con gli esempi di campi statici pubblici e privati del report usando documentation.js 13.1.1. Traccia il modo in cui documentation.js analizza e assegna i nomi ai campi statici privati, quindi confronta la posizione generata con la documentazione prevista nell’ambito della classe. Il lavoro è completato quando il campo privato è documentato sotto la sua classe senza renderlo pubblico.

Scritto dal modello di indicizzazione a partire dal testo della issue.