Feat: Add FF for note session bar component (MRs)

What does this MR do and why?

This MR is a follow up from adding this BE FF and after the addition of this component (that has been rolled out). Steps are the same as the previous FE MR,

References

Related GitLab MRs and Work Items:

• backend FF rollout MR: !252355 (merged)
• FF Work Item: #624349
• Work Item for bug fix: gitlab-org#22699
• Previous MR rolled out for note-session-bar: !249824 (merged)

Screenshots or screen recordings

See this parent MR: !249824 (merged)

How to set up and validate locally

For DAP/General Setup

• General DAP: https://docs.gitlab.com/development/duo_agent_platform/
• Assigning Duo to a group: https://docs.gitlab.com/development/ai_features/#run-gitlabduosetup-script
• Make sure you are in SaaS mode with export GITLAB_SIMULATE_SAAS=1 set in your env.runit file in your local gdk.
• Turn on the following feature flags (if necessary): duo_workflow, duo_workflow_in_ci, ai_flow_triggers.

Adding Sessions

1. A: If you see no Sessions, you can trigger one that displays a Pipeline/Job by going to an Issue within your Duo enabled project and clicking the Generate MR with Duo button. It should trigger a new session that you can open up.
2. B: You can also run the following query bundle exec rake "gitlab:duo_workflow:populate[50,20,1,<<YOUR_TEST_GROUP_PATH_HERE>>]" to create new agent sessions. Refresh the page. Make sure the group you are testing in has Duo assigned (see DAP setup above).

Test Comments (The Actual Testing)

1. Make sure you are in a Duo enabled projects where Sessions permissions have been set.
2. Be sure to enable the following FF note_agent_session_bar. You can use the following to toggle it on/off: http://gdk.test:3000/rails/features/
3. The below has already been implemented and works, but just needs a FF around it for now to fix a few things.

Test New Comments

1. Go to any Work Item (Left rail: Work items, then select a Work Item)
2. In the comments area, type a new comment and tag an agent (ex: @duo-developer could you count to 10)
3. See the new Session status bar displays when a Session starts (ignore the comment status for the time being).
4. Validate a new Session has started in your Side Panel sessions tab.
5. Click the Session bar and validate a new tab opens with the Sessions page (avoided going to Side Panel as any user could click this and Side Panel is specific only to the user)
6. When the Session completes, the bar goes away. If the Session fails, the bar will still display with an error status. If the Session is awaiting input, the bar will still display with awaiting input message (follow up, add waiting reasoning).

Test Existing Comments

1. Go to any Work Item (Left rail: Work items, then select a Work Item)
2. In the comments area, find an existing comment and tag an agent in a thread (ex: @duo-developer could you count to 10)
3. See the new Session status bar displays when a Session starts (ignore the comment status for the time being).
4. Validate a new Session has started in your Side Panel sessions tab.
5. Click the Session bar and validate a new tab opens with the Sessions page (avoided going to Side Panel as any user could click this and Side Panel is specific only to the user)
6. When the Session completes, the bar goes away. If the Session fails, the bar will still display with an error status. If the Session is awaiting input, the bar will still display with awaiting input message (follow up, add waiting reasoning).

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #624326 (closed)