Update file path part 2 (#6)

## Changes

Updating the path to reference a locally stored file as opposed to
reference the copy on my local computer (this is a hack I did to get off
the ground)

This is a follow up PR because:
- Some of the paths are not correct
- I want the api spec file to have the same naming convention as the
java repo

## Motivation

This will enable us to publish the SDKs

https://vanta-team-j1bu05uk.atlassian.net/browse/PEX-4217

Author: dangitschris

.devcontainer/README.md

@@ -20,11 +20,11 @@ The speakeasy CLI allows you to generate more usage snippets. Here's how:
 - To generate a sample for a specific operation by providing an operation ID, use:
 
 ```
-speakeasy generate usage -s api-spec.yaml -l typescript -i {INPUT_OPERATION_ID} -o ./samples
+speakeasy generate usage -s api_spec.yaml -l typescript -i {INPUT_OPERATION_ID} -o ./samples
 ```
 
 - To generate samples for an entire namespace (like a tag or group name), use:
 
 ```
-speakeasy generate usage -s api-spec.yaml -l typescript -n {INPUT_TAG_NAME} -o ./samples
+speakeasy generate usage -s api_spec.yaml -l typescript -n {INPUT_TAG_NAME} -o ./samples
 ```

.devcontainer/setup.sh

@@ -27,4 +27,4 @@ EOL
 echo "$TS_CONFIG_CONTENT" > samples/tsconfig.json
 
 # Generate starter usage sample with speakeasy
-speakeasy generate usage -s api-spec.yaml -l typescript -o samples/root.ts
+speakeasy generate usage -s api_spec.yaml -l typescript -o samples/root.ts

.speakeasy/gen.yaml

@@ -2,7 +2,7 @@ configVersion: 2.0.0
 generation:
   devContainers:
     enabled: true
-    schemaPath: api-spec.yaml
+    schemaPath: api_spec.yaml
   sdkClassName: Vanta
   maintainOpenAPIOrder: true
   usageSnippets: