🌱 Update the internal solver before exporting

[m1kola]

Related to #161

Preparing the internal solver to be exported and used without the DeppySolver wrapper.

[codecov]

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (e676cce) 63.90% compared to head (13066d1) 64.43%.

Files	Patch %	Lines
internal/solver/solve.go	93.33%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #164      +/-   ##
==========================================
+ Coverage   63.90%   64.43%   +0.53%     
==========================================
  Files          11       11              
  Lines         482      478       -4     
==========================================
  Hits          308      308              
+ Misses        155      152       -3     
+ Partials       19       18       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[everettraven]

These changes look good to me. That being said, I'm not well versed with the entire system and interactions in deppy so another approval is probably good to have prior to merging (I don't think my approval actually counts for merging in this repo anyways)

[ncdc]

Is it possible to get here?

[m1kola]

I'm not sure. My guess is that Deppy used to accept context for some reason (maybe somehow related to entity sources). So this is probably a leftover from the times where some call coud be cancelled.

I did a bit of code archaeology with a goal to find out the origin of this on Friday, but without any results. I decided to leave this error for now, but removed exported ErrIncomplete. I think for the scope of this PR it is good enough. But I will dig deeper into this (will create an issue to track this). Edit: see #167

[ncdc]

This PR is definitely a step in the right direction. We can resolve whether to use a context or not later.