chore(refactor): code styling

[v0lkc]

Purpose

While working on #850 I noticed some deviations in regards of how we name certain functions. This PR solely addresses code styling and doesn't change the behavior of the provider in any way.

• ran go fmt ./...
• globalaccount instead of globalAccount
• subaccount instead of subAccount
• a few test functions were wrongly named
  • TestResourceRolCollectionAssignment
  • TestResourceSubAccountRoleCollection
  • ...

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[x] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

• Test the code via automated test

go test ./...

• Additional test steps

...

What to Check

Verify that the following are valid:

• Automated tests are executed successfully

• ...

Other Information

Checklist for reviewer

The following organizational tasks must be completed before merging this PR:

• The PR is assigned to the Terraform project and a status is set (typically "in review").
• The PR has the matching labels assigned to it.
• The PR has a milestone assigned to it.
• If the PR closes an issue, the issue is referenced.
• Possible follow-up items are created and linked.

[lechnerc77]

lgtm