Filter Integration Issues After Transition to MFEs

Some filters are not functioning correctly after transitioning from Django legacy views to MFEs. Here are a few examples found during testing with the openedx-filters-samples repository when trying to halt the registration, login and unenrollment:

• StudentRegistrationRequested: when a user’s registration is halted, no feedback is provided to the user. Although the registration is successfully blocked, users can only see the reason by inspecting the network console.

• StudentLoginRequested: when a user’s login is halted, the interface displays a generic error message stating "an error occurred." The message doesn’t explain why the login failed or what went wrong.

• CourseUnenrollmentStarted: when an unenrollment is halted, the frontend incorrectly shows that the unenrollment was successful, even though it wasn't because of the exception raised by the filter. The unenrollment doesn’t complete as it should, but this isn’t reflected in the UI.

• CertificateCreationRequested: the UI fails completely in a development environment, showing a 400 AxiosError with no useful feedback.

These issues result in a confusing user experience, as users cannot understand why their actions are blocked. Improving the feedback provided by these filters is crucial for better clarity and consistency.