Replaces most links and Hamilton references

[skrawcz]

This replaces all links with the right ones.

Changes

• changes most repo links to the correct one
• Updates most Hamilton -> Apache Hamilton

How I tested this

• inspected

Notes

• This does not replace the hamilton.dagworks.io links until we have hamilton.apache.org set up and running.

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future TODOs are captured in comments
• Project documentation has been updated if adding/changing functionality.

[skrawcz]

@apache/hamilton-committers I think the docs are in a reasonable state to commit. There's more work to get the apache things we need in, but I've done a lot of changes here that I think are good enough to commit.

I'd squash merge this PR with a nice commit upon approval.

[skrawcz]

note: the unit tests are failing due to some kedro library change...

[elijahbenizzy]

Should we use Hamilton or Apache Hamilton when referring to the core features? I.E. the library's name isn't changing -- it's still a "Hamilton Node" not an "Apache HAmilton Node"? Otherwise looks good.

[jernejfrank]

Just a minor comment/question on the domain from my side since I saw that some files already use https://hamilton.apache.org/

[skrawcz]

@elijahbenizzy @jernejfrank I think I addressed your concerns.

[elijahbenizzy]

@skrawcz guidance on naming:

You don't need to use Apache Hamilton everywhere. It's good to start
with Apache Hamilton and in some cases even Apache Hamilton
(incubating).
It is ok to shorten to Hamilton later in the doc. I would generally
use Apache Hamilton in headings but inside paragraphs, it may be
better to use Hamilton - although first reference in the paragraph -
might be best to stick with Apache Hamilton.

[skrawcz]

@skrawcz guidance on naming:

You don't need to use Apache Hamilton everywhere. It's good to start
with Apache Hamilton and in some cases even Apache Hamilton
(incubating).
It is ok to shorten to Hamilton later in the doc. I would generally
use Apache Hamilton in headings but inside paragraphs, it may be
better to use Hamilton - although first reference in the paragraph -
might be best to stick with Apache Hamilton.

Yes. I'm not going to go through the docs with a fine toothed comb here. I err'ed on the side of too much Apache Hamilton. Which I think is fine. We can always adjust this as we touch and read the docs...

[jernejfrank]

LGTM, I will let @elijahbenizzy approve