Toolkit provides feedback when packaging without a successful build (#1472)

A previous update to the toolkit allowed it to `sam package` and `sam deploy` even if a `sam build` failed (e.g. if you have a simple NodeJS Lambda without a `package.json` file). This pops a toast to alert the user that this is occuring.

Author: bryceitoc9

package.nls.json

@@ -419,6 +419,7 @@
     "AWS.samcli.deploy.general.error": "An error occurred while deploying a SAM Application. {0}",
     "AWS.samcli.deploy.workflow.init": "Building SAM Application...",
     "AWS.samcli.deploy.workflow.packaging": "Packaging SAM Application to S3 Bucket: {0}",
+    "AWS.samcli.deploy.workflow.packaging.noBuild": "Attempting to package source template directory directly after \"sam build\" failed",
     "AWS.samcli.deploy.workflow.stackName.initiated": "Deploying SAM Application to CloudFormation Stack: {0}",
     "AWS.samcli.deploy.workflow.start": "Starting SAM Application deployment...",
     "AWS.samcli.deploy.workflow.success": "Successfully deployed SAM Application to CloudFormation Stack: {0}",

src/lambda/commands/deploySamApplication.ts

@@ -167,6 +167,15 @@ async function packageOperation(
     },
     buildSuccessful: boolean
 ): Promise<void> {
+    if (!buildSuccessful) {
+        vscode.window.showInformationMessage(
+            localize(
+                'AWS.samcli.deploy.workflow.packaging.noBuild',
+                'Attempting to package source template directory directly since "sam build" failed'
+            )
+        )
+    }
+
     getLogger('channel').info(
         localize(
             'AWS.samcli.deploy.workflow.packaging',