Remove remaining eos.io references from docs portal

[nsjames]

We want to remove all remaining references to eos.io

https://docs.google.com/spreadsheets/d/1IYbcQFBV1DPCvhcxJZcgzzqwK7PaC2hCywgOMi2fxiM/edit#gid=711758493

AC:

• Identify where remaining links to eos.io are
• Replace all references to eos.io with our docs URLs
  • Ensure you are using the right branch that the docsgen is using (check scripts)
• Ask Val to recrawl staging after merges

Note: Check repositories that are used by the docsgen: https://github.com/eosnetworkfoundation/docsgen/tree/main/scripts

[lparisc]

Old directories previously deployed on the AWS server still remain after being removed from the source repos and rebuilt. For instance, there were still old welcome, ko, zh folders produced from old builds - the welcome repo has long been renamed to docs and non-eng locales disabled. Therefore, I had to delete these dead folders directly from the AWS web server to remove the eos.io references since removing them from the source repos won't do it.

[lparisc]

Removed last pesky eos.io references from docs portal. Notes: with the exception of the swift reference, regenerated successfully after replacing the eos.io links, I ended up replacing most eos.io links directly within the AWS production site. Rationale: both staging and production site reuse most repo branches, so rebuilding production would produce a mixed production/staging site w/ inaccurate contents/links. We need a way to clearly specify default repo/branches to use for staging vs. production, and allow overrides passed to the clean_rebuild.sh script.

[lparisc]

Also notified the appropriate stakeholder to please re-run the crawler to double-check.