As suggested, Support ticket is indeed required to correct this feature/issue.
A possible workaround could be to resolve component links yourself in your application code. This can done as Alvin mentioned, using separate GraphQL queries (instead of relying on DXA Model Extension/Service).
This would roughly translate to following steps for a DXA-based application.
i) Disable link resolving for Rich text format area in DXA Model Extention/Serive.
Make sure following properties are set in the dxa.propertiesdxa.properties
of your DXA Model Service/Extension
dxa.defaults.rich-text-xmlns-remove = false
dxa.defaults.rich-text-resolve = false
(See SDL docs: Rich-text link handling by the DXA Model Extension or standalone Model Service)
In RTF, the links would be unresolved with link tags.
For example:
<a xlink:href="tcm:1-11">link text</a>
ii) Parse and resolve links in RTF using PCA Client (for GraphQL queries)
@Autowired
private ApiClientProvider pcaClientProvider;
String resolvedLink = pcaClientProvider.getClient().resolveDynamicComponentLink(ContentNamespace.Sites, publicationId, pageId, componentId, templateId, true);