Design and implement rate limiting policy

- https://github.com/dandi/dandi-archive/issues/1891
showed the need for means to either balance out or just to limit "heavy users" of the API server. A quick attempt is being worked on in
- https://github.com/dandi/dandi-archive/pull/1899
to provide a quick mitigation to that issue, but it is just a stop gap measure.

As many other public (or paid) services have rate limiting, we can and should have one too.

- it needs to be designed with current utilization patterns in mind to not cause unnecessary slow downs etc. May be it could be somehow made to be enforced only/when server experiencing high load etc. The point is that it should not unnecessarily complicate/negatively effect access to our services.
- well documented and described in the [Terms & Polices](https://www.dandiarchive.org/handbook/about/terms/)
- dandi-cli should be ensured to continue working, gracefully handling rate limiting, and possibly alerting users about need to authenticate to gain better access, or consider composition of more efficient scripts, etc.