fix!: typos in API naming

[gekkedev]

• stopRecoring -> stopRecording
• GroupNotificationType.Inivite -> GroupNotificationType.Invite
• a little bit of spelling/grammar changes

This change might make a lot of code incompatible, so maybe it is better to save this for the next major release?

Before merging; I think I found one more potential typo:
https://github.com/gekkedev/wppconnect/blob/76baaca6fcb824b26f94a12339c3fda0ef7d5129/src/api/layers/sender.layer.ts#L145
Should be "error" in my opinion, but: Is this key from the platform or is it created by WPPC?

[icleitoncosta]

So, since the function name is already incorrect, we cannot change it because it will break the current users. In this case, we have to leave it as it is until we release a more comprehensive breaking change.

[gekkedev]

what if I prepare a deprecation instead so that no one else starts using the methods/enums with typos and uses the correct name?

1. rename the function/enum to have the correct name
2. create an alias that refers to the correct name and add the @deprecated flag

[manfe]

LGTM, enum is not even being used.