fix: Make allowed_actions_config optional

[Danielku15]

Resolves #2105

---

Before the change?

• For the two resources resource_github_actions_repository_permissions and resource_github_actions_organization_permissions the allowed_actions_config values were considered mandatory if allowed_actions was set to selected

After the change?

• For the two resources resource_github_actions_repository_permissions and resource_github_actions_organization_permissions the allowed_actions_config values are optional in all scenarios.
• On a read operation of these resources, when allowed_actions_config is not set on the declared resource, it will not be loaded from the API and the respective properties will not be filled and available for further usage. The behavior is aligned with the other allowed_actions values.

Pull request checklist

• [x] Tests for the changes have been added (for bug fixes / features)
• [x] 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
• [x] No

---

[Danielku15]

@kfcampbell Problem should be fixed now. I adapted two things:

• Instead of the API information I now rather look at the state/input whether the actions config should be loaded.
• In import/initial read scenarios there might be no info in the state. There I load now the information.

Its a bit tricky to handle as it seems there is no good way to get the values as defined in code (desired state).