Update meek-azure name and description

Meta Issue for tracking the meek-azure to meek rename.

---

Tasks in rough timeline/dependency order:

• communications; explain migration/upgrade path and timeline:
  • send emails:
    • Guardian Project, tor-dev
  • open issues:
    • CalyxOS: https://gitlab.com/CalyxOS/calyxos/-/issues/3400
    • OnionShare: https://github.com/onionshare/onionshare/issues/2044
    • Ricochet-Refresh: https://github.com/blueprint-freespeech/ricochet-refresh/issues/249
      • fixed in 3.0.36
    • Orbot: https://gitlab.com/guardianproject/tormobile/orbot/-/issues/18
    • OnionBrowser: https://github.com/OnionBrowser/OnionBrowser/issues/527
• tor browser strings: tor-browser#44069 (closed)
• community; updates to website:
  • Tor Browser manual:
    • tpo/web/manual#187 (closed)
  • Support Portal
  • Community
  • Snowflake pages
• simultaneous:
  • tor-browser: TorSettings migration logic to move existing meek-azure usage to meek usage
  • tor-browser-build: update pt_config.json with new name
    • tor-browser-build#41532 (closed)
  • rdsys: handle/map requests for meek-azure to meek (i.e. for legacy systems still using the old name)
    • tpo/anti-censorship/rdsys#272 (comment 3231854)
• blog post
  • overview of the meek-azure to meek name change (targeted to developers, could be opportunity for broader comms if that's desired)