[Cloud Security] Assign default GCP account type

[jeniawhite]

Proposed commit message

In order to have a working GCP integration, we are required to have an account type.
Older integrations did not have this value, this caused a breaking change.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Related issues

• Closes [Cloud Security] CSPM GCP migration to multi-account config is broken kibana#169098

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-10-17T12:56:30.655+0000

• Duration: 15 min 45 sec

Test stats 🧪

Test	Results
Failed	0
Passed	4
Skipped	0
Total	4

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (0/0)	💚
Files	100.0% (0/0)	💚
Classes	100.0% (0/0)	💚
Methods	25.0% (2/8)	👎 -66.463
Lines	100.0% (0/0)	💚 3.688
Conditionals	100.0% (0/0)	💚

[elasticmachine]

Package cloud_security_posture - 1.6.4-preview1 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture

[elasticmachine]

Package cloud_security_posture - 1.6.4 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture