docs: Add information about registryMappingRules usage by Registry Connect (#7766)

* Add information about Registry Connect

* ci: auto-formatting prettier issues

* ci: auto-formatting prettier issues

* Update installer-reference.md

* ci: auto-formatting prettier issues

* ci: auto-formatting prettier issues

* Update installer-reference.md

* ci: auto-formatting prettier issues

* Fix according to review

* Update installer-reference.md

* ci: auto-formatting prettier issues

* Update installer-reference.md

* ci: auto-formatting prettier issues

---------

Co-authored-by: Svetlana Efimova <svetlanaefimova@Mac.lan>
Co-authored-by: svetlana-efimova <205686560+svetlana-efimova@users.noreply.github.com>
Co-authored-by: vault-token-factory-spectrocloud[bot] <133815545+vault-token-factory-spectrocloud[bot]@users.noreply.github.com>

Author: 3 people

docs/docs-content/clusters/edge/edge-configuration/installer-reference.md

@@ -173,7 +173,7 @@ were downloaded when creating the [content bundle](../edgeforge-workflow/palette
 :::info
 
 <!-- prettier-ignore -->
-Palette will automatically update the image path when <VersionedLink text="Harbor Edge-Native Config" url="/integrations/packs/?pack=harbor-edge-native-config" />  pack is enabled. For example, if you have a registry mapping rule such as the following.
+Palette will automatically update the image path when <VersionedLink text="Harbor Edge-Native Config" url="/integrations/packs/?pack=harbor-edge-native-config" /> or <VersionedLink text="Registry Connect" url="/integrations/packs/?pack=registry-connect" />  pack is enabled. For example, if you have a registry mapping rule such as the following.
 
 ```yaml
 "us-docker.pkg.dev/palette-images": "example.registry.com/palette-images"
@@ -184,6 +184,16 @@ Then the image tag will be updated with the prefix URL to the primary registry,
 specified in the user data. This allows the Edge host to find and pull images that came from an external registry
 through the primary registry.
 
+<!-- prettier-ignore -->
+Note that the Harbor Edge-Native Config pack is deprecated and will be removed in a future release. Refer to
+[Migrate from Harbor Edge-Native Config Pack](../site-deployment/deploy-custom-registries/migrate-edge-native-config.md)
+for guidance on transitioning to Registry Connect.
+
+The Registry Connect pack additionally supports `imageReplacementRules` (defined in the pack YAML under
+`charts.registry-connect.config.registry.imageReplacementRules`), which serve the same purpose as
+`registryMappingRules`. If you provide both settings, the configuration in `imageReplacementRules` takes precedence over
+`registryMappingRules`.
+
 :::
 
 ```yaml