Recommend Secure Messaging over SecureDrop in callouts

[rtyley]

What does this change?

Updates the secure-anonymous-submission link on Callout components (like the one on this page: https://www.theguardian.com/business/2025/oct/01/airline-industry-workers-share-your-experiences#6311788 - components which are currently used solely by the Community Team):

• From: SecureDrop https://www.theguardian.com/securedrop
• To: Secure Messaging https://www.theguardian.com/tips - detailing Secure Messaging/Coverdrop, as well as other communication options including SecureDrop (page initially setup in January 2025) (note from @hoyla : In running text we use the convention "Secure Messaging" even though the logo itself is "SecureMessaging".)

Why?

I noticed today that callouts on www.theguardian.com still point to SecureDrop - Secure Messaging represents a generally more user-friendly way to submit tips securely & anonymously than the steps required for submitting to SecureDrop, so ideally, if readers want to use high-security routes like this, we should offer them Secure Messaging for preference. Note that the new link is to a page that still lists SecureDrop as an option, as it is better for, eg, submitting files, photos, etc.

As these Callout components are used by the Community Team, we'll need to check they're ok with the change, and ensure they have access to read Secure Messaging messages intended for them.

Screenshots

Before	After

Related

For subsequent/separate PRs:

• SecureDrop is also in many footer definitions in this project (a refactor might be a good idea to reduce duplication?)
  • From @hoyla about SecureDrop footers/headers: "Part of the convention for all SecureDrop sites is to include that info in such places" - so we should retain them.
• This wording is also in a mobile-apps-api template: https://github.com/guardian/mobile-apps-api/blob/3d9f47cb7bd6e0a7c9e7e1deb64bbd07121d4198/common-play/src/main/scala/views/campaigns/callouts/calloutForm.scala.html#L97

[github-actions]

Deploy build 45506 of Mobile::mobile-apps-rendering to CODE

All deployment options

• Deploy build 45506 of Mobile::mobile-apps-rendering to CODE
• Deploy parts of build 45506 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[github-actions]

Deploy build 21266 of dotcom:rendering-all to CODE

All deployment options

• Deploy build 21266 of dotcom:rendering-all to CODE
• Deploy parts of build 21266 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[github-actions]

Hello 👋! When you're ready to run Chromatic, please apply the run_chromatic label to this PR.

You will need to reapply the label each time you want to run Chromatic.

Click here to see the Chromatic project.

[hoyla]

In running text we use the convention "Secure Messaging" even though the logo itself is "SecureMessaging".

[gu-prout]

Seen on PROD (merged by @rtyley 7 minutes and 56 seconds ago) Please check your changes!