Remove Microsoft Azure AI Personalizer provider from the Recommendation Service

[iamdharmesh]

Description of the Change

As the Microsoft Azure AI Personalizer service will be retired on October 1, 2026, and users have not been able to create new Personalizer resources since September 20, 2023, this provider only works for users who had configured a Personalizer resource before that date.

This PR removes the Microsoft Azure AI Personalizer provider from the Recommendation Service, along with the "Recommended Content" block (New "Recommended Content" based on embeddings will remain as it is).

Note

We may want to pause on merging this PR if we decide to continue supporting the Azure AI Personalizer provider. However, since users have not been able to create new Personalizer resources for the past two years, and we likely don’t have many active users of it, this seems like the right time to remove it. That said, I’m open to keeping it for a while longer, or until the Personalizer service is officially retired by Microsoft.

Closes #890
Closes #769

How to test the Change

1. Go to Tools > ClassifAI > Recommendation Service > Recommended Content Settings.
2. Verify that the "Microsoft Azure AI Personalizer" provider is no longer available for configuration.
3. Configure the Recommended Content feature using embeddings and ensure it works properly to validate that this PR does not break anything.

Changelog Entry

Removed - Microsoft Azure AI Personalizer provider from the Recommendation Service

Credits

Props @dkotter @jeffpaul @vikrampm1 @fabiankaegy @iamdharmesh

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added Critical Flows, Test Cases, and/or End-to-End Tests to cover my change.
• All new and existing tests pass.

[dkotter]

We may want to pause on merging this PR if we decide to continue supporting the Azure AI Personalizer provider. However, since users have not been able to create new Personalizer resources for the past two years, and we likely don’t have many active users of it, this seems like the right time to remove it. That said, I’m open to keeping it for a while longer, or until the Personalizer service is officially retired by Microsoft

Personally I'm fine with removing this. I'm not sure really anyone used this in the first place (unfortunately) and with it being retired by Azure, doesn't seem worthwhile for us to keep the code around.