Use libsonata to resolve node sets

[joni-herttuainen]

No description provided.

[joni-herttuainen]

@GianlucaFicarelli Tell me what you think. If this looks somewhat ok, I'll update the docs and add changelog entries. Should we bump this up a major version bearing in mind we will also change {nodes,edges}.get?

[codecov-commenter]

Codecov Report

Merging #213 (dfeb452) into master (2da1c6d) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #213   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           29        29           
  Lines         2163      2159    -4     
=========================================
- Hits          2163      2159    -4     

Flag	Coverage Δ
pytest	100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
bluepysnap/circuit.py	100.00% <100.00%> (ø)
bluepysnap/frame_report.py	100.00% <100.00%> (ø)
bluepysnap/node_sets.py	100.00% <100.00%> (ø)
bluepysnap/nodes/node_population.py	100.00% <100.00%> (ø)
bluepysnap/simulation.py	100.00% <100.00%> (ø)

[mgeplf]

Things look reasonable to me, but I haven't been following it as closely as @GianlucaFicarelli - IMO he should have the final say.

[GianlucaFicarelli]

LGTM 👍

Should we release 1.0.7 before merging and releasing 1.1.0?
Alternatively, the changelog should be updated (moving the entries from 1.0.7 to 1.1.0, after rebasing on master)

[joni-herttuainen]

I'm happy with merging and releasing any none-breaking changes first

[GianlucaFicarelli]

I'm happy with merging and releasing any none-breaking changes first

I'd like to merge #220 once it's approved (since it's not a breaking change), release 1.0.7, then merge this PR and release 1.1.0. What do you think?

[joni-herttuainen]

Sounds good. I think #220 is good to go.

[GianlucaFicarelli]

LGTM