[SNOW-224] Remove CI race condition

[philerooski]

Currently, our CI job executes all its jobs at once, although the order in which those jobs runs may be important. I added needs fields to each job which should wait for the successful completion of another job before running. I also removed some unused, commented-out lines and reordered the jobs in the ci.yaml file itself so that they are ordered according to the order in which they will execute (this is why it looks like the changes are more drastic than they really are).

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[danlu1]

Thanks so much for working on it. It looks good to me. My understanding is the we will implement changes for objects in the datawarehouse (dev and prod) before fine tuning/ updating account level setting to avoid privilege issue when modifying the datawarehouse.

[philerooski]

@danlu1 That's one way of looking at it. I tried to mirror the order in which schemachange applies versioned vs. repeatable scripts:

1. non-admin schemachange scripts
2. admin schemachange scripts
3. admin snowsql scripts

(3) is analogous to schemachange repeatable scripts, which normally run after schemachange versioned scripts, so we mirror that behavior here in the ordering 2 → 3.