xml parser skips files with DOCTYPE entries

```
> Task :my-module:gatherModuleInfo
e: Invalid xml file my-module/src/main/res/values/strings.xml
line 4; column 10: DOCTYPE is disallowed when the feature "http://apache.org/xml/features/disallow-doctype-decl" set to true.

]>
```
Then later we can refer to these standard entity names in the strings:
```
One last thing…
```
In this case, we prefer to use `…` here, because it is more meaningful for translators, and it is more grammatically correct. I.e., using `…` vs `...`. It also translates differently for some languages - for example, some languages prefer a different type of ellipsis, like the midline (`⋯`) or vertical ellipsis (`⋮`).

Inlining the unicode character can often be difficult for people reading the file to understand that it is a unicode character rather than its similar non-unicode counterpart (i.e., `'` apostrophe vs `’` right-single quotation or rsquo), which is why we use the `&#<>;` notation. And inlining that notation into the string, someone reading the file won't understand what that number represents unless they look it up.

So the workaround is using the named XML entity: it gives us the exact unicode representation, with a meaningful name, without compromising the character width which can have an impact on some older editors that aren't well equipped to handle multi-byte unicode characters.

Beginne mit dem Code hinter der :my-module:gatherModuleInfo-Aufgabe und der Analyse von my-module/src/main/res/values/strings.xml. Prüfe, wie der XML-Parser mit dem gemeldeten DOCTYPE umgeht, und füge Tests für benannte Entitäten wie … hinzu. Erledigt ist die Aufgabe, wenn die Datei statt übersprungen zu werden geparst wird und die benannten Entitäten in Strings nutzbar bleiben.

Vom Indexierungsmodell aus dem Issue-Text verfasst.