Fix JSON-LD entity type comparison to be case-insensitive

[samalisam-novu]

Summary

The json_ld_entity button group field in the site defaults Blueprint stores lowercase keys (organization, person), but the comparisons in Cascade::jsonLd() checked against capitalized strings (Organization, Person). Since PHP's === is case-sensitive, the JSON-LD Organization and Person structured data snippets were never rendered.

Changes

• Normalize json_ld_entity value with strtolower() before comparison in Cascade::jsonLd(), making the check case-insensitive
• Update existing test to use lowercase entity values matching what the Blueprint actually stores
• Add tests for uppercase entity values to ensure backward compatibility

Steps to reproduce

1. Set the JSON-LD entity to "Organization" and provide an organization name in SEO Pro site defaults
2. Query an entry via GraphQL:

   query {
     entry(site: "de", uri: "", collection: "pages") {
       seo {
         html
       }
     }
   }

3. The html field contains no <script type="application/ld+json"> tag with the Organization schema

Expected: A JSON-LD Organization snippet should be present in the output.

[duncanmcclean]

Thanks for the pull request!

The JSON LD entity should always be lowercase though, so I've reverted your commits and adjusted the code.

seo-pro/src/SiteDefaults/Blueprint.php

Lines 111 to 114 in b045a7a

	'options' => [
	'organization' => __('seo-pro::messages.organization'),
	'person' => __('seo-pro::messages.person'),
	],

They were incorrectly title case to start with (#440) but it was fixed in #458.