[SaaS] Add specific availability for SNI Rewrite (cloudflare#23725)

* [SSL] Update custom-origin.mdx

* [SSL] Update index.json

Author: ngayerie

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin.mdx

@@ -10,8 +10,6 @@ import { GlossaryTooltip, Render } from "~/components"
 
 <Render file="custom-origin-server-definition" />
 
-<Render file="ssl-for-saas-plan-limitation" />
-
 ## Requirements
 
 To use a custom origin server, you need to meet the following requirements:
@@ -25,6 +23,8 @@ To use a custom origin, select that option when [creating a new custom hostname]
 
 ## SNI rewrites
 
+<Render file="ssl-for-saas-plan-limitation" />
+
 When Cloudflare establishes a connection to your default origin server, the `Host` header and <GlossaryTooltip term="Server Name Indication (SNI)">SNI</GlossaryTooltip> will both be the value of the original custom hostname.
 
 However, if you configure that custom hostname with a custom origin, the value of the SNI will be that of the custom origin and the `Host` header will be the original custom hostname. Since these values will not match, you will not be able to use the [Full (strict)](/ssl/origin-configuration/ssl-modes/full-strict/) on your origins.

src/content/plans/index.json

@@ -2779,6 +2779,13 @@
 					"biz": "Yes",
 					"ent": "Yes"
 				},
+				"sni_rewrite": {
+					"title": "[SNI Rewrite for Custom Origin](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/#sni-rewrites)",
+					"free": "No",
+					"pro": "No",
+					"biz": "No",
+					"ent": "Contact your account team"
+				},				
 				"custom_certificates": {
 					"title": "[Custom certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/)",
 					"free": "No",