Kickoff of a new season of development for AsyncAlgorithms; Share

[FranzBusch]

@vanvoorden

Maybe this is more of a feedback for the diff review… but do we know what kind of horizontal dependencies we expect between share and the rest of the package? Could this potentially ship in a "subpackage" target under AsyncAlgorithms so that a product engineer that needs only share could link just against that code and not pay a binary size and compile time penalty for code they might not need?

This has come up before and we could leverage package traits to move each algorithm behind a trait and enable all by default. This would allow other packages to only pick the algorithms they need.