Add Programmable Tokens page - #913

Thanks Aldo, the page is well structured and the i18n wiring is clean. Before we can merge, a few things need attention.

Content accuracy

• KYC FAQ: allow-listed users are described as "not allowed to hold, send, or receive". That reads inverted.
• CIP-0143 credit: the CIP lists Philip DiSarro, the repo README credits "Phil DiSarro and the IOG team". We probably want to match that.
• "Bank of International Settlements" should be "Bank for International Settlements" (two places). The sentence "Not a manual check and not a permissioned wrapper" appears twice.
• Please replace the em and en dashes in the copy with commas, colons or periods, per the style guide.

Logo strip

• The strip under the hero shows Eternl, GeroWallet, CardanoScan, BloxBean and BendingAI without a visible label (only the screen reader label calls them "partners and users"). Partners of whom? Visitors will read it as these projects supporting programmable tokens today. I wonder if this is the right way to do it, also please see my next point.
• How is this strip meant to be maintained going forward? Do we add every project that implements CIP-113, and if so, what is the bar (mainnet integration, a public announcement, something else) and who decides? Without clear criteria the strip will either go stale or turn into a selection we cannot justify.

Assets

• Please don't create a page-named folder for assets that are shared by nature. Company logos go into static/img/logos/<slug>.svg plus <slug>-dark.svg as vectors, so other pages can reuse them.
• There is already a noise texture at static/img/layer-2/noise.png. Please reuse one texture (we can move it to a shared location) instead of adding a second.
• The six orb SVGs are single translucent circles, a CSS radial gradient would do the same without extra files.
• Open graph image is missing.

Components and styling

• The three call-to-action buttons are custom styles with fixed colors and no dark-mode handling, so they look different from the rest of the site and do not follow the theme. Please use the standard button button--primary button--lg classes (or CtaOneColumn for a white button on a blue band), as on the other pages. The same applies to the bands behind them, which keep their light-mode colors in dark mode.
• The HorizontalScroller padding change applies to every carousel on the site (apps, categories, events). Please confirm those still look right, or scope the change to this page.
• We already have FAQSection and GovernanceFAQ. Could the FAQ use one of them rather than a new Accordion?

Happy to help with any of this.