feat(rcs): implement baseline Asterism and Constellation stubs

[Ahavahdev1]

This PR introduces the missing baseline components required for Google Messages to provision RCS successfully over microG.

• Implemented AsterismService stub.
• Implemented ConstellationService stub.

[Mickmick21]

I smell this PR as being AI slop.
First you replace an API key with "YOUR_API_KEY_HERE" ? This is for me the biggest sign it's AI.

Second, the ""fix"" is is two classes that contains two things and doesn't even do anything, and the single comment is in portuguese that says something along the lines of "Actual implementation of the Stub Binder to satisfy RCS IPC calls."

Note that I could be wrong, but I'm just going to put this here :

[Ahavahdev1]

Hi @Mickmick21, thanks for the review and the sharp eyes. I completely understand your concern.
The YOUR_API_KEY_HERE was an accidental commit from my local debugging/mitmproxy environment where I was isolating the API calls. That was careless on my part, and I will revert it immediately.
Regarding the empty stubs and the localized comment: I accidentally pushed my raw draft. However, the technical reasoning behind pushing baseline stubs for AsterismService and ConstellationService is that Google Messages crashes during the initial RCS provisioning handshake if it cannot resolve these Binders. By simply exposing these service endpoints, we can bypass the initial ServiceNotFoundException and force the client to proceed to the next stage of the provisioning state machine.
I will clean up the PR, revert the API key placeholder, remove the localized comments, and structure the services properly to match microG's architecture. I'll push the corrections shortly. Thanks again for the feedback