Added note on write_suites API access token scope to README

[james2791]

With the addition of the Test Suite resource in v0.22.0, one's API access token that is used to interact with the provider needs to additionally have the write_suites scope for said API token to create/update and delete suites (interaction with the REST API)

[jradtilbrook]

@james2791 I think this is documented in a few places that will need updating as well. And to confirm, it doesn't need read_suites because it uses GraphQL for that side of things right?

[james2791]

@james2791 I think this is documented in a few places that will need updating as well. And to confirm, it doesn't need read_suites because it uses GraphQL for that side of things right?

Just added to the other spots - correct too: the Read of the Test suite resource being node based, this more for the C-U-D ops otherwise that interacts with REST