serving 404 response (rather than a 410) for /future-labs microsite

[marjisound]

A query from CoPipLand. We received a request from CP about serving a 404 response (rather than a 410) from the /future-labs microsite. https://www.theguardian.com/future-labs

Reported by @groakland in webex channel
link to chat: https://chat.google.com/room/AAAAG9rU0m0/4oOUZUqNnas/4oOUZUqNnas?cls=10

Also requested by CP: https://groups.google.com/a/guardian.co.uk/g/dotcom.platform/c/Ayf77mQs4D4

Task list

• Check the microsite has no content (including expired) associated to it in the Content API (ask the content-platform team to check Elasticsearch)
• Check that other pieces of content don't refer directly to the microsite page. For example, articles containing links.
• Check our github repo for references to the microsite. We occasionally find hardcoded references to tag pages.
• Providing that is okay delete the microsite directly in Dynamo.
• The microsite will also need to be deleted in Elasticsearch of CAPI.
• The redirect will need to put in place (CP does this).

[domlander]

Added a PR to update the docs: guardian/tagmanager#543