Unify the node and dataflow versioning API

[zilto]

Motivation described in #728 and relates to #175.

Changes

• moved the hash_source_code() and the utility remove_docs_and_comments() from grap_utils to graph_types
• added to graph_types.HamiltonNode and graph_types.HamiltonGraph a .version property
• updated code that depended on these functions and the related tests
• updated the hamilton.plugins.h_experiments.hook.ExperimentTracker to use the HamiltonGraph.version implementation to align with CLI and DiskCache

How I tested this

• ran the full test suite successfully after edits

Notes

• some code path use the hash_source_code() directly on functions/Callables or on hamilton.node.Node

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.

[ellipsis-dev]

👍 Looks good to me!

• Performed an incremental review on 248f191
• Looked at 93 lines of code in 1 files
• Took 1 minute and 37 seconds to review

More info

• Skipped 0 files when reviewing.
• Skipped posting 1 additional comments because they didn't meet confidence threshold of 50%.

1. tests/test_driver_export.py:109:

• Assessed confidence : 0%
• Comment:
  Good job on updating the test to dynamically set the version attribute of each node in the EXPECTED_JSON. This ensures that the test will pass regardless of the Python version used.
• Reasoning:
  The test test_export_execution has been updated to reflect the changes in the PR. The version attribute of each node in the EXPECTED_JSON is now dynamically set to the version of the corresponding node in the graph. This is a good change as it ensures that the test will pass regardless of the Python version used, as the version attribute is dependent on the Python version. I don't see any issues with this change.

Workflow ID: wflow_9buXnjTWmOPF5dWT

---

Not what you expected? You can customize the content of the reviews using rules. Learn more here.

[ellipsis-dev]

👍 Looks good to me!

• Performed an incremental review on a60db44
• Looked at 21 lines of code in 1 files
• Took 2 minutes and 23 seconds to review

More info

• Skipped 0 files when reviewing.
• Skipped posting 1 additional comments because they didn't meet confidence threshold of 50%.

1. tests/test_driver_export.py:107:

• Assessed confidence : 100%
• Grade: 40%
• Comment:
  Consider creating a deep copy of EXPECTED_JSON within the test and modify that instead of the global variable to avoid side effects.
• Reasoning:
  The test test_export_execution modifies the global EXPECTED_JSON variable in each run. This could lead to unexpected results if multiple tests use this variable or if the test is run multiple times in the same session. It would be better to create a deep copy of EXPECTED_JSON within the test and modify that instead.

Workflow ID: wflow_2Otbj2mKo61mztca

---

Not what you expected? You can customize the content of the reviews using rules. Learn more here.

[elijahbenizzy]

A few thoughts, but overall good