A4A: Remove a4a-help-center feature flag

[jkguidaven]

Context: pfSQfS-1sJ-p2

Proposed Changes

This pull request removes the feature flag for the "a4a-help-center" and makes the Help Center functionality always enabled in the A8C for Agencies sidebar. It also cleans up related conditional code, removes unused styles and configuration, and simplifies the sidebar and profile dropdown components.

Key changes include:

Help Center Feature Flag Removal:

• Removed the a4a-help-center feature flag from all configuration files, making the Help Center always enabled. [1] [2] [3] [4]
• Eliminated all conditional checks for isEnabled('a4a-help-center') in the codebase, so Help Center components are always rendered. [1] [2] [3] [4]

Sidebar and Profile Dropdown Simplification:

• Removed the conditional rendering and associated logic for showing the Help Center and support contact widgets, streamlining the sidebar and profile dropdown UI. [1] [2] [3]

Code and Style Cleanup:

• Deleted unused imports and removed obsolete CSS classes and styles related to the previous conditional UI for the profile dropdown. [1] [2] [3] [4] [5] [6] [7] [8]

These changes ensure the Help Center is consistently available and reduce code complexity by removing feature flag checks and related UI branching.

Why are these changes being made?

• Ensures our codebase are maintainable by removing irrelevant codes.

Testing Instructions

• Use the A4A live link and navigate to /overivew page.
• Verify that there is no regression on the Help center functionality.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-171838

Jetpack Cloud Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-171838&env=jetpack

Automattic for Agencies Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-171838&env=a8c-for-agencies

Dashboard Live (dotcom) (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-171838&env=dashboard

Dashboard Live (CIAB) (direct link)

https://calypso.live/ciab?image=registry.a8c.com/calypso/app:build-171838&env=dashboard

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• help-center
• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug remove/a4a/help-center-feature-flag on your sandbox.