gRPC.jl monorepo

[csvance]

@tanmaykm I'm getting gRPCServer.jl ready to register and think it would be better to setup a gRPC.jl mono repo to avoid code duplication / simplify testing. I'd like to split things into three packages:

1. gRPCCore.jl
2. gRPCClient.jl
3. gRPCServer.jl

Would something like that be acceptable? We are also not allowed to start without a capital letter for registration anymore, so I'm trying to figure out what to do about that. Renaming gRPCClient -> GRPCClient seems worse than just having an inconsistent naming convention between the package names.

[tanmaykm]

Sure, a gRPC.jl monorepo makes sense to keep things together. There was an earlier package with the same name: https://github.com/tanmaykm/gRPC.jl. It was not registered though. I am not using it anymore, and it does not seem like anyone else is. So having a gRPC.jl monorepo in JuliaIO would not be a problem.

I see that the package naming guidelines only recommend that the name start with a capital letter. But since in this case gRPC is a well known framework, keeping that as the package name does seem natural and intuitive. The automatic merge rules may not allow it, but we can check with the registry maintainers and JuliaIO org admins.

Would be good to check with others too.. cc: @StefanKarpinski @mbauman @DilumAluthge

[csvance]

I used Claude to help setup an initial mono-repo for testing purposes here: https://github.com/csvance/gRPC.jl

Of course I need to review, test, and benchmark absolutely everything. But the general structure at least should be representative of the end goal.