[GCP] Fix bootstraping

Type of change

• Bug Fix
• Feature

Does this introduce a change in the core logic?

• [Yes]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Updates description?

Fix GCP bootstrap:

1. Change requested memory
2. Fix SSDMS URL
3. Change node pools
4. Add possibility to pass idToken to SSDMS.

NOTE: At least for GCP, you must specify your idToken in the request to Workflow Service to access SSDMS during Segy-Zgy conversion.

{
    "executionContext": {
        "Payload": {
            "AppKey": "test-app",
            "data-partition-id": "{{data-partition-id}}"
        },
        "sd_svc_api_key": "{api-key}",
        "storage_svc_api_key": "{api-key}",
        "filecollection_segy_id": "{{data-partition-id}}:dataset--FileCollection.SEGY:<id>:",
        "work_product_id": "{{data-partition-id}}:work-product--WorkProduct:<id>:",
        "id_token": "{{id_token}}",
        "data_partition_id": "{{data-partition-id}}"
    }
}