How about the Mozilla Public License (MPL)? Might be a decent middle ground.
Pros: It requires modifications to your code to be open-source, but it allows companies and individuals to combine your library with proprietary code, provided the proprietary parts are kept separate. This could encourage more adoption while still ensuring your core contributions remain open.
Cons: MPL is less restrictive than GPL or AGPL, so some companies may still use your library in proprietary systems.
If you want to foster collaboration however I would avoid GPLv3 - and favor GPLv2. V3 basically is a license that actually IMHO stifles collaboration because as the “owner” of the code base you could technically yank the ability to use the library from a contributor at any time (at least in my understanding). I don’t have a problem with that per se but the authors should have given it a new name rather than co-opt the V2 reputation.