What license to choose for an open-source project?

Question

open source

Good day
There was a question about choosing a license for our project. The bottom line is that it will consist of three parts: two of which will be open source and the ability for everyone to connect to the project. The third part (we are talking about the security module) will also be open source BUT (!) Access to the code will be either from third-party developers who have passed a certain check or from company employees assigned to this part of the project. The project will also be monetized through the purchase of various services. Also planned is the ability for end users to write their own modules (which can be both open source and closed source and distributed both for free and for free)
Ideally, I would like to bring everything down to GPLv3 or Apache 2.0, but there is no certainty that this will be possible. Plus, the question remains with the possibility of patenting some ideas and developments (the possibility of free use, distribution and modification will be indicated)
Which of the licenses will be the best way to suit this task or will you need your own "bike"?

Answer 1

The third part (we are talking about the security module) will also be open source BUT (!) Access to the code will be either from third-party developers who have passed a certain check or from company employees assigned to this part of the project.

So the third part will be closed.
Will the first 2 parts work without the closed third? If not, then what's the point of opening the first two?
There is one more thing that affects the choice of license - which third-party libraries will be used in your project and what licenses they have. If third-party libraries have a GPL license, then you can’t jump from the GPL anywhere and there is essentially no choice.

Answer 2

MIT or BSD allows everyone to receive money for it, but the code also remains open,
but this is all for lawyers, because it is not known how money will be received from the program

Answer 3

if the code cannot be received by an arbitrary person, it is not open :)
so think the other way.
you can make an "open" code in the form of read-only accessibility, and give the entry to the repository to the merchants. then you will get something you want.
in principle, licenses govern the user's access to source codes.
and the conditions for making user changes to the original source code are left to the author.