feat: data organization secret repositories

[moutonjeremy]

Resolves no issue

This PR add a new data for retrieve the list of repositories of a secret of an organisation.

---

Before the change?

• It's not possible to have the repositories list for a secret.

After the change?

• Data action for get the repositories list for a secret

Pull request checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes
• No

---

[kfcampbell]

Can you talk to me a little more about the use case for this and why you want to add it to the provider? In general, I'm a little wary of adding new resources/data sources without issues and discussion beforehand.

[moutonjeremy]

For my use case, we have a process to init/create (automatically) services (and repos) via a template but we must give access to a secret for each repo.
The service creation process is independent for each service, so we cannot manage access to the secret in centralized mode, so we must know the previous state before making a modification.
This is not an ideal situation.

[moutonjeremy]

Hello, will the PR be reviewed or will it be refused?