Change Details

This removes the need for passing config as a function argument through the whole validation stack, when a reference is already available via `ChainstateManager.options`. There are more places where this can be applied, but I noticed the diff is starting to get big, so let's do the rest in separate diffs.

This removes the need for passing config as a function argument through the whole validation stack, when a reference is already available via `ChainstateManager.options`. In this diff we apply this idea to `AcceptToMemoryPool`, `ProcessNewPackages` and `ConnectTip` (and to the whole stake of functions that needed a `Config` for the only purpose calling these 3) There are more places where this can be applied, but I noticed the diff is starting to get big, so let's do the rest in separate diffs.

This removes the need for passing config as a function argument through the whole validation stack, when a reference is already available via `ChainstateManager.options`. In this diff we apply this idea to `AcceptToMemoryPool`, `ProcessNewPackages` and `ConnectTip` (and to the whole stake of functions that needed a `Config` for the only purpose calling these 3) There are more places where this can be applied, but I noticed the diff is starting to get big, so let's do the rest in separate diffs.