Add `test/config.ts` and `package.json` patterns to load `.env` only when intended

@austinkelleher pointed out some time ago that it's not ideal to always load .env when running yarn test. This has proven to be true in a few situations. Instead, the developer that wants to perform recordings with the .env loaded (real credentials) will use yarn test:env, and the build will use yarn test:ci.

Move the integration template to this pattern:

[ ] package.json scripts:

"test": "jest",
"test:env": "LOAD_ENV=1 yarn test",
"test:ci": "yarn lint && yarn type-check && yarn test",

[ ] test/config.ts (example):

import * as dotenv from 'dotenv';
import * as path from 'path';
import { IntegrationConfig } from '../src/config';

if (process.env.LOAD_ENV) {
  dotenv.config({
    path: path.join(__dirname, '../.env'),
  });
}

export const integrationConfig: IntegrationConfig = {
  jamfHost:
    process.env.JAMF_HOST || 'https://jupiteronedev.jamfcloud.com/?failover',
  jamfUsername: process.env.JAMF_USERNAME || 'test-username',
  jamfPassword: process.env.JAMF_PASSWORD || 'test-password',
};

[ ] .github/workflows/build.yml

      - name: Run tests
        run: yarn test:ci

[ ] Any *.test.ts that needs the configuration:

import { integrationConfig } from '../../../test/config';

JupiterOne / integration-template

Add `test/config.ts` and `package.json` patterns to load `.env` only when intended #29