Migrating to ProvableHQ and Provable URLs

[onetrickwolf]

Motivation

Migrate Aleo URLs and packages to Provable. Keep Aleo references when referring to the Aleo network, this change is just to reflect moving the SDK to Provable Inc. (the company).

Example of distinction: Things referring to the company like @aleohq with be migrating @provablehq but things referring to the network like create-aleo-app will remain since it's referring to the Aleo network and creating an app for the Aleo network.

Test Plan

• [x] SDK published and working links and references
• [x] WASM published and working links and references
• [x] Aleo.tools properly redirects to Provable.tools and all links updated
• [ ] create-aleo-app examples work (this may be a stretch goal since some were previously not working)
• [x] All CICD checks pass
• [x] Website compiles and deploys properly

[onetrickwolf]

https://www.npmjs.com/package/@provablehq/wasm and https://www.npmjs.com/package/@provablehq/sdk published. Going to test then probably increment and republish before flagging aleohq packages as deprecated.

[onetrickwolf]

It looks like there's some weird spurious test failures.

But otherwise this LGTM

Yeah @Pauan the failures were from tests hitting the network and checking for accounts that existed in testnet3 but not in testnet-beta. I talked to @iamalwaysuncomfortable about this and we probably shouldn't have unit tests that are hitting the network. We can just set up a stub or something and if we really want to check the network maybe make it an e2e that runs on merge as a sanity check. But yeah I don't really want test flake from network availability. I disabled the test for now.

[onetrickwolf]

@christianwwwwwwww is going to fix the create-aleo-app examples in another PR, was a bit too much to fit in this one.