Add rate limiting and baseurl

[TimDiam0nd]

This ensures that consumers will not have to manually manage their own rate limiting.

Currently its a rudimentary 60 a minute; the documentation doesn't explicitly show what the rate limits are for the new v1alpha endpoints, if you guys have any more information regarding this i would appreciate it (will also reach out to our csm).

Finally, adding the base url session means that there is no need to write:

    url = f"{client.base_url}/{client.instance_id}/rules/{rule_id}"

Instead, you can just do:

    url = f"rules/{rule_id}"

(or probably just do it inline e.g. session.get(f"rules/{rule_id}"))

[emeryray2002]

some of the legacy API's sadly have a different format. Also, different APIs have different quota settings, which can vary by customer, making rate limiting hard. Also not sure we could import that 3P rate limiting extension on top of the google requests library. Are you facing rate limiting issues? If so, what methods?

[TimDiam0nd]

I did hit some rate limiting issues that were due to something stupid i was doing, when i got the idea.
In the past with the old chronicle api i used this as i would regularly hit the 60 requests a minute limit with e.g. updating rules, reference lists, parsers/extensions.

But upon reflection i dont think the new API is as strict as that as it uses the normal gcp quotas, so im more than happy to remove it (but would like to leave the base url thing as that would save a lot of effort).

For the legacy APIs, we can just continue doing it as is. If a full url is passed it will override the base url.