split out into multiple crates + rename

[Emilgardis]

I think I want to split the library into multiple parts.

I also want to if possible use a better name, twitch_api2 is only used because twitch_api was taken

e.g

come up with a name, say foo, and then

• twitch_types (this should probably be just that as it should be pretty generic)
• foo_helix
• foo_eventsub
• foo_pubsub
• foo_core
  implements all "base" types used for above crates.
• foo
  implements the rest, e.g clients and their actions

[Emilgardis]

@simonsan would you two be willing to give me access to twitch_api on the crates.io registry? If deemed necessary we could also transition as you mentioned in #27 (comment) to an organization. I've pre-allocated twitch-rs for that.

also ping @Nerixyz who might be interested in this effort

[simonsan]

Sorry for late reply, sent an invite on crates.io and would prefer the org on Github, also for future maintainability.

[Emilgardis]

Awesome! I've accepted the invite!

I'll get to moving everything over to the new org later then, I'll send out invites to the org for you. If there's anyone else interested reach out to me. Message here, rustc zulip (Emilgardis) or mail works

[simonsan]

Joined the org, feel free to push this crate to twitch_api crate on crates.io. ;-)

Might make sense to yank the other pushed versions beforehand.

[simonsan]

I yanked all the old versions:
https://crates.io/crates/twitch_api/versions

So it's ready to push to whenever you feel like :) @Emilgardis

[Emilgardis]

Once 0.7.0 is out for real, need to mark twitch_api2 as deprecated. Possibly also issue a audit advisory