[Sonarr] match with CF

[8a8al00ey]

Pull request

Purpose Match with CF

Approach If this Pull Request is created to solve a issue explain how does this change address the problem?

Open Questions and Pre-Merge TODOs Check all boxes as they are completed

• [ ] Use github checklists. When solved, check the box and explain the answer.

Learning If you're adding a new Custom Format make sure you follow the Radarr/Sonarr Custom Format (JSON) Guidelines.

Requirements Check all boxes as they are completed

• [x ] These changes meet the standards for contributing.
• [ x] I have read the code of conduct.

[TRaSH-]

i think we should use [ ] and not use space on L10+L25+L32

[8a8al00ey]

Basically just copied over: https://github.com/TRaSH-/Guides/blob/7aae5ecd12a30ffd3e10561d6ef4736546707baf/docs/json/sonarr/cf/atvp.json#L13

[TRaSH-]

Need to add the regex also to the guide, the Release Profile regex isn't automatically updated when changing the JSON. Where with the Custom Formats it does. Will try to do it this weekend.

[nuxencs]

Need to add the regex also to the guide, the Release Profile regex isn't automatically updated when changing the JSON. Where with the Custom Formats it does. Will try to do it this weekend.

Updated the PR with the needed changes to the Sonarr guide.