Use the neighborlist in signac core

[cbkerr]

Description

Motivation and Context

This enables ignoring certain state point keys when detecting neighbors

Checklist:

• I am familiar with the Contributing Guidelines.
• I agree with the terms of the Contributor Agreement.
• The changes introduced by this pull request are covered by existing or newly introduced tests.
• The package documentation and framework documentation in signac-docs are up to date with these changes.
• I have updated the changelog and added any related issue and pull request numbers for future reference.

[bdice]

Nice work! Can we add test coverage? (I know dashboards are hard to write tests for... maybe you can get an agent to help.) Otherwise a few small fixes should do it.

[cbkerr]

I refactored some repeated code in the tests to make it easier to add tests...and caught an untested case in the ignore in core! (constant state point parameters). I'm catching it in the test as an expected warning for now to document it before the next signac release

[janbridley]

Does this indicate that the code will no longer work for some schemas? I don't mind either way, but it's worth noting

[cbkerr]

This was moved to signac core. There, it's what allows it to detect neighbors for state points changing within heterogenous/disjoint etc project schemas, but does not detect differences of only adding/deleting a state point key.

For example

# just jobs a1 and a2 are detected as neighbors of each other
a1 = project.open_job({"a": 1}).init()
a2 = project.open_job({"a": 2}).init()
a2b1 = project.open_job({"a": 2, "b": 1}).init()

nl = project.get_neighbors()
assert nl[a1.id]["a"][2] == a2.id
assert nl[a2.id]["a"][1] == a1.id
assert nl[a2b1.id]["a"] == {}

[janbridley]

Requested a few small things to review, but overall this looks great! Very excited to have this in