Retrieve the events list for a project for v2

[boozec]

Sorry to re-open a PR for the same feat, but I can't re-open #1047. This PR adds

Manage events on Sentry.

USAGE:
    sentry-cli events [OPTIONS] <SUBCOMMAND>

OPTIONS:
        --auth-token <AUTH_TOKEN>    Use the given Sentry auth token.
    -h, --help                       Print help information
        --header <KEY:VALUE>         Custom headers that should be attached to all requests
                                     in key:value format.
        --limit <LIMIT>              Limit of requests [default: 10]
        --log-level <LOG_LEVEL>      Set the log output verbosity. [possible values: trace, debug,
                                     info, warn, error]
        --max-rows <MAX-ROWS>        Max of rows for a table.
    -o, --org <ORG>                  The organization slug
    -p, --project <PROJECT>          The project slug.
        --quiet                      Do not print any output while preserving correct exit code.
                                     This flag is currently implemented only for selected
                                     subcommands. [aliases: silent]
    -t, --tags                       Include tags into the list.
    -u, --user                       Include user's info into the list.

SUBCOMMANDS:
    help    Print this message or the help of the given subcommand(s)
    list    List all events in your organization.

As requested on this comment I added two flags:

• limit is the limit of API requests
• max_rows is the limit of events the table will print (default is all)

I'm not really sure about the last flag but I think it is the closets thing to "per-page" as cursor moves 100 items at a time.

---

@kamilogorek sorry if I could only work on it now but I was a bit busy 😅

[kamilogorek]

I'll try to patch everything today

[kamilogorek]

We already have all those types in sentry-sdk crate.

[boozec]

Hi @kamilogorek I found Event but I don't think you're talking about this one because it is not good for this JSON response.
For EventUser you were right because we can use sentry::protocol::User instead of EventUserOption.
For EventTags I suggest to keep the Vec<EventTag> due the JSON serialization. If we use the same way used for sentry-sdk we have to refactor tags in Vec<BTreeMap<String, String>> (or HashMap) but we always have a BTreeMap (or HashMap) with a tuple ("key", "...") and a ("value", "...") cause the nature of the response.

[kamilogorek]

Fixed everything, applied necessary changes and added basic cli tests. Thanks for your contribution!