[3.1 -> main] Curate eosio refs, and github, eosnetwork links (docs)

[lparisc]

Resolves eosnetworkfoundation/devrel#28
Resolves eosnetworkfoundation/devrel#29

[ericpassmore]

Once approved the changes in this branch should be patched into the 3.1 release branch as well.

[spoonincode]

If a change is destined for a release branch, it should go to the release branch first. And then a merge commit should be created in a PR targetting main. Some recent examples are #194 & #198 as well as #183 & #189

[lparisc]

If a change is destined for a release branch, it should go to the release branch first. And then a merge commit should be created in a PR targetting main. Some recent examples are #194 & #198 as well as #183 & #189

Ok sure thing - thanks for the PR samples. I saw the closed PRs earlier and realized there were no backport PRs, like [main -> 3.1]. I'm not sure why since these are fixes not new features (so backports should be fine), but I will apply it in the order you suggest: release branches first, then main (develop).

[spoonincode]

Yeah it's a change in branch strategy compared to the old EOSIO repo & b1

[lparisc]

Closing this PR to recreate a new one to avoid rewriting history.