add support for require conversation resolution

[marcoieni]

This setting was set manually from the UI. With this PR we add in team the ability to set this field via toml.

As you can see from the screenshots, all the repositories edited here have "require conversation resolution before merging" checked.
So we are just encoding this information in the toml files.

As you can see from the empty dry run, no changes will be done to GitHub. However if you check the last edit of the dry run (before I pushed the changes to the toml files), you can see that the dry run was correctly detecting these repos.

[github-actions]

Dry-run check results

[WARN  rust_team::sync] sync-team is running in dry mode, no changes will be applied.
[INFO  rust_team::sync] synchronizing crates-io
[INFO  rust_team::sync] synchronizing github

[marcoieni]

In another PR, Kobzol said that adding new fields is not a breaking change for triagebot 👍

[marcoieni]

Links of branch protections edited in this PR:

https://github.com/rust-lang/blog.rust-lang.org/settings/branch_protection_rules/68112349
https://github.com/rust-lang/docs.rs/settings/branch_protection_rules/70108634
https://github.com/rust-lang/promote-release/settings/branch_protection_rules/26750749
https://github.com/rust-lang/relnotes/settings/branch_protection_rules/28495006
https://github.com/rust-lang/thorin/settings/branch_protection_rules/23222430

[marcoieni]

Branch protections screenshots

[rustbot]

rust_team_data/src/v1.rs has been modified, it is used (as a git dependency) by multiple sub-projects like triagebot, the www.rust-lang.org website and others.

If you are changing the data structures, please make sure that the changes are not going to break serde deserialization (adding a field is fine; removing or renaming a field isn't).

If you must do a breaking change to the format, make sure to coordinate it with all the users of the rust_team_data crate.