feat(subscriptions): Use RPC in subscriptions pipeline

[shruthilayaj]

Updates the subscription pipeline to support RPCSubscriptionData.

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
2535	1	2534	5

View the top 1 failed tests by shortest run time

tests.subscriptions.test_subscription.TestEAPSpansRPCSubscriptionCreator::test[EAP spans RPC subscription]

Stack Traces | 0.184s run time

Traceback (most recent call last):
  File ".../tests/subscriptions/test_subscription.py", line 397, in test
    identifier = creator.create(subscription, self.timer)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ".../snuba/subscriptions/subscription.py", line 36, in create
    data.validate()
  File ".../snuba/subscriptions/data.py", line 189, in validate
    raise InvalidSubscriptionError("Multiple project IDs not supported.")
snuba.datasets.entity_subscriptions.validators.InvalidSubscriptionError: Multiple project IDs not supported.

To view more test analytics, go to the Test Analytics Dashboard
Got feedback? Let us know on Github

[shruthilayaj]

hack for now, we want to round this to the lowest available granularity (15s) more context here

[shruthilayaj]

I'll add more validation in a follow up so it's easier to review

[volokluev]

Why can the create subscription RPC call not be its own PR?

[shruthilayaj]

Why can the create subscription RPC call not be its own PR?

@volokluev Creating a subscription requires validation, so I needed to build and run the request before storing it. That introduces the RPCSubscriptionData class. And basically once I introduced it in one place, I kinda had to follow all the typing issues and handle it everywhere.

[shruthilayaj]

build_request returns generic type TRequest and run_query accepts TRequest.
So for SnQLSubscriptionData, build_request returns Request and run_query accepts Request
and for RPCSubscriptionData, build_request returns TimeSeriesRequest and run_query accepts TimeSeriesRequest