Reword CDN duplicate-rendering changelog entry for clients

Start the entry with "Fixed" and drop the sentence about internal lfint-
selectors, which describes the implementation; point to the Changed entry,
which already covers the client-visible renamed inner elements.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: Paolo Argentieri

CHANGELOG.md

@@ -5,7 +5,7 @@ Licensed under the MIT License. See LICENSE in the project root for license info
 
 ### Fixes
 
-- In the CDN custom-element build, every component the library instantiates inside another component rendered twice: once from the parent's Angular view and once from the browser upgrading the same host element. `lf-field-container` showed two template pickers and two "Add/remove fields" blocks, `lf-repository-browser` held a second empty breadcrumbs bar, and 28 of the 35 registered tags were affected. Library components now declare an internal `lfint-` selector that the library renders instead of the registered tag. The registered tag names, element properties and the `lf-` selectors Angular templates use are unchanged.
+- Fixed an issue in the CDN custom-element build where every component the library instantiates inside another component rendered twice: once from the parent's Angular view and once from the browser upgrading the same host element. `lf-field-container` showed two template pickers and two "Add/remove fields" blocks, `lf-repository-browser` held a second empty breadcrumbs bar, and 28 of the 35 registered tags were affected. The registered tag names, element properties and the `lf-` selectors Angular templates use are unchanged; the inner elements the library renders are renamed, as described under **Changed**.
 - The CDN bundle (`lf-ui-components.js`) is now wrapped in a function scope, so its minified top-level declarations are no longer created as globals. On a page that shares `window` with other bundles, such as SharePoint, anything that later assigned one of those short names replaced the library's own binding, and the next component creation failed with an error such as `Rx is not a function`, leaving the custom element un-upgraded and its methods missing. Custom element registration and the source map are unaffected.
 - `lf-field-template-container` and `lf-field-adhoc-container` no longer report `ExpressionChangedAfterItHasBeenCheckedError` (NG0100) in development mode when a host calls `initAsync` from `ngAfterViewInit`. `lf-field-adhoc-container` could also leave its "no additional fields" message on screen for a moment after rendering fields.