Feature/latest and active

[miratepuffin]

What changes were proposed in this pull request?

1. Added a latest() function on all classes which equates to x.at(graph.latest_time)
2. Exposed is_active on edge, edges, and node as a short hand to see if the entitiy has any updates within the window - this is not added only nodes as they are filtered through windows so it would basically always return true.
3. Add event_graph function to Graph and persistent_graph function to PersistentGraph - these are basically just noops, but make it so in python you can call them without knowing what type you current have.

TODO:

• Need to add all of the above to graphql

Why are the changes needed?

• It is a massive pain (expecially in graphql) to always look up the current time or latest time in the graph
• It can often be the case (say when doing a rolling) that you end up with an 'Empty' edge/node - this is done becuase dealing with Nones is a pain in the ass - so is_active() allows you to check this.

Does this PR introduce any user-facing change? If yes is this documented?

Yes and yes

How was this patch tested?

New tests

Issues

Created #1787

Are there any further changes required?

This has opened a couple of questions on if other filters should apply a window, and how should the DSL filtering be read.

[github-actions]

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Rust Benchmark'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 2.

Benchmark suite	Current: f5885c2	Previous: b992030	Ratio
lotr_graph_subgraph_10pc/max_degree	48261 ns/iter (± 6862)	22968 ns/iter (± 1168)	2.10
lotr_graph_subgraph_10pc_materialise/materialize	825371 ns/iter (± 87894)	225687 ns/iter (± 4926)	3.66
lotr_graph_window_50_layered/max_id	49804 ns/iter (± 3959)	22137 ns/iter (± 1414)	2.25

This comment was automatically generated by workflow using github-action-benchmark.

[ljeub-pometry]

LGTM

[ljeub-pometry]

latest time in the Graph