Remove the in-app feedback button in Production, QA and Dev

Remove the in-app feedback button (the prelaunch issue reporter) from the Coach Pulse consumer application in Production, QA and Dev. Widened from the original Production-only scope. A per-environment config flag is preferred over deleting the component so it restores without a deploy. Demo is NOT covered and needs a call before the work starts. Demo is still the surface the Asia markets and SMC Macau run on. Scope: C1. Remove the button entry point everywhere it renders in Production, QA and Dev. C2. Close the submission path in all three: form route and endpoint not reachable by direct link, stale clients get a clear rejection. C3. Hold Demo until the scope call is made. If Demo comes in, it joins C1 and C2 as a fourth environment. C4. Route content-type feedback (previously going to Chanel's team through the button) via the ServiceNow help desk. C5. Update training documentation and the user guide to carry the ServiceNow path and drop the temporary-availability language. C6. Leave the localized strings in place across all 15 languages, marked inactive. C7. Reflow the surface where the button sat, checked at mobile and tablet widths in each environment. C8. Keep analytics history intact and note the cutover date. Known trade: removing it from QA means the build team loses the in-context reporter during launch week, so launch-week findings get described by hand with no auto-attached screenshot, device or page context. Open questions: Demo in or out (blocks starting) · Sarah's sign-off, since the Aug 18 Asia tech call landed on keeping the button live for the first week or two after launch and this reverses that · how QA reports issues instead · removal vs flag-based hide · overlap with the Settings Help and Support removal shipping in the same release · whether admin and FutureProof accounts keep a reporting path · release lane and CAB date ahead of the Aug 22 launch. Spec doc: CoachPulse_FeedbackButton_Removal_Spec_v2.docx (supersedes v1)