fix: enable ids in list of features from landing page

[derberg]

Ids are critical for Google Tag manager. They are used to track how often people click on certain links on landing pages. The purpose is to learn if these are even useful if people care and interact with them.

cc @alequetzalli this is a fix for the issue we discussed recently. So basically answer is: there is no global issue with website that id are disabled. It was just a problem with single component after brand migration. So you can easily use id in tag manager

@alequetzalli the problem is I have no idea how we can make sure ids are not removed by anyone in next PRs. Without automation it can happen in future that these are removed. The only option I see is making you codeowner for docs related code. But this is not best solution, just responsibility is delegated to you 😄
Else? we could introduce automated tests. So start website instance, and check if id are there. You would have a config file where you have to write what id you add, and where are they expected to be 🤔

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	52f938f
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/636affff445cdc0008ce63ae
😎 Deploy Preview	https://deploy-preview-1087--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🔴 Performance	33
🟠 Accessibility	88
🟠 Best practices	83
🟢 SEO	100
🔴 PWA	30

Lighthouse ran on https://deploy-preview-1087--asyncapi-website.netlify.app/

[quetzalliwrites]

Point 1
Question: I don't understand the following sentence 😂✌🏽 "So basically answer is: there is no global issue with website that id are disabled."

Point 2
Yes, go ahead and make me codeowner for docs related changes, even outside of md files. I honestly have been leaning toward asking for that anyways, so it will be useful either way. 🙌🏽 I am already honestly a core leader, if you will, in all Docs UX and DevEx changes, so this honestly just makes sense.

Point 3
I think we should use IDs and educate our community on why we need these. Adding an automation test that checks for removed IDs in PRs sounds logical to me.

[akshatnema]

/rtm

[derberg]

@alequetzalli

Point 1
oh sorry, when we had a call last week I shared that it might be that id are blocked globally like ignored by next.js maybe. That was one of my worst suspicions. Luckily I was wrong.

Point 2

#1089

Point 3

#1090