Adjust project name in login view for chatbot route

[mabashian]

Jira Issue: https://issues.redhat.com/browse/AAP-50250

Assisted-by: claude-code

Description

This is a bit of a messy "problem" to solve. The project name comes in via a setting which we append to the end of "Log in to " on the login page. The approach I've taken is to check to see if the ?next query param starts with /chatbot and then find/replace the intended text with an empty string. I don't think this is a particularly clever approach nor is it robust. If the setting (ANSIBLE_AI_PROJECT_NAME) string changes just a bit, this logic may break. I also don't love hard-coding references to WCA in the view. I'm open to suggestions for alternative ways to achieve this (or push back saying that this is a bad idea and we shouldn't do it).

Testing

1. Pull down the PR
2. Make sure that ANSIBLE_AI_PROJECT_NAME is set to 'Ansible Lightspeed with IBM watsonx Code Assistant' (note that I also had to add - ANSIBLE_AI_PROJECT_NAME=${ANSIBLE_AI_PROJECT_NAME} to compose.yml)
3. Run the ai-connect-service
4. Navigate to /login (should see the full project name)
5. Navigate to /chatbot unauthenticated (should be redirected to /login and see the name without the WCA bits)

Scenarios tested

1. Login screen renders correctly when no "next" param present
2. Login screen renders correctly when "next" param is something other than /chatbot
3. Login screen renders correctly when "next" param starts with /chatbot

Production deployment

• This code change is ready for production on its own
• This code change requires the following considerations before going to production:

[manstis]

Have you thought of an inverse approach, i.e. add " with WatsonX blah blah" if Wisdom Service is configured to use WCA? All AI features are defined in "ModelPipelines" and each has a Provider ID. It'd be quite simple to iterate them and check for wca or wca-onprem and add the extra text.

I'm not at my laptop now but can talk more later if you're interested.

[mabashian]

@manstis that's an interesting idea - let me take a look at that as an alternative. That sounds like it could be a more clean solution.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[goneri]

Good enough for now.

[mabashian]

OK so the plan is to merge this PR and then revert it in #1734 and address this with a proper fix. This should be good enough for now and #1734 won't change the UX (just fix the technical debt).