Statsbombpy

This release upgrades the API version number for the following endpoint:
`player-match-stats` -> `v5`

**What's new?**

The following fields have been added to player_match_stats:

- `player_match_ccaa`: Claims or CCAA%(Claimable Collection Attempts over Average), is a measure of how likely the
goalkeeper is to attempt to claim a "claimable" pass, versus the average goalkeeper attempted claim rate
- `player_match_claim_success`: How many of a goalkeeper’s claim attempts are successful
- `player_match_da_aggressive_distance`: An average value of how far forward from the goal a goalkeeper is coming to
perform defensive actions.
- `player_match_goals_conceded`: How many goals a goalkeeper conceded (doesn’t include penalties or own goals)
- `player_match_gsaa`: How many goals did the keeper save/concede versus expectation (post-shot xG faced)
- `player_match_gk_positioning_error`: How far on average a goalkeeper is from the optimal position for facing a shot
- `player_match_positive_outcome_score`: How frequently is the player involved in sequences that resolve with a positive outcome (shot, free kick in the attacking half or a corner) while on the pitch
- `player_match_npot_psxg_faced`: How much non-penalty on-target post-shot xG a goalkeeper faced
- `player_match_save_ratio`: Percentage of on-target shots that were saved by the goalkeeper
- `player_match_gsaa_ratio`: The measure of goals saved above average, as a percentage of shots faced by the
goalkeeper
- `player_match_npot_shots_faced`: How many non-penalty on-target shots a goalkeeper faced

Add missing events and formations fields to sb.lineups()

This release adds functionality to interact with the new team match stats endpoint, which provides aggregated data at the team-match level. It is only available to customers with API access.

This update fixes a bug with certain 360 frames where the variable `distances_from_edge_of_visible_area` is `None`. Previously, the `sb.frames()` function couldn't handle such instances and would return an error for that match.

This release adds substitution info to the event functions.

Variables added:
- `substitution_outcome_id`
- `substitution_replacement_id`

This release adds `pass_recipient` info to events.

v.1.11.0
This release upgrades the API version numbers for the following endpoints:
`matches` -> `v6`

**What's new?**

Collection Status added to Matches in Competition API.
To help customers find out where a match is in the collection pipeline we have added a new field `collection_status` to the “matches in competition” API. There are 16 collection status options available, which are listed in detail in Appendix 3 in the “Matches in Competition” API documentation




v.1.10.1
This patch adds a status check to the public API calls.

Previously when a user entered the wrong match or competition and season id into the open data functions you get the following error:
`JSONDecodeError: Extra data: line 1 column 4 (char 3)`

Instead, we've added a status check to all the public API calls so that if, for example, the user passes through an invalid `match_id` we get a `HTTPError 404` returned to indicate that they've tried to access a resource that doesn't exist.