Go from "Artifact Repository" to "Package Firewall" (#269)

This change updates the page names, slugs, language, and links to use
the "Package Firewall" product term instead of "Artifact Repository."
This update is made in concert with changes in the `aviary` repo and
their releases will need to be coordinated.

Additional changes made include:

* Update `CONTRIBUTING.md` to specify how to initialize submodules
* Add a site announcement about the Phylum to Veracode transition

Author: maxrake

CONTRIBUTING.md

@@ -65,23 +65,34 @@ Here's how to set up the Phylum `documentation` repository for local development
     git clone [email protected]:phylum-dev/documentation.git
     ```
 
-2. Create a branch for local development:
+2. Initialize and pull the git submodules
+
+    ```sh
+    ## Populate submodules initially
+    git submodule update --init --recursive
+
+    ## Update submodules during development
+    git fetch --all
+    git pull --recurse-submodules
+    ```
+
+3. Create a branch for local development:
 
     ```sh
     git checkout -b <name-of-your-branch>
     ```
 
     Now you can make your changes locally.
 
-3. Commit your changes and push your branch to GitHub:
+4. Commit your changes and push your branch to GitHub:
 
     ```sh
     git add .
     git commit -m "Description of the changes goes here"
     git push --set-upstream origin <name-of-your-branch>
     ```
 
-4. Submit a pull request (PR) through the GitHub website
+5. Submit a pull request (PR) through the GitHub website
 
 ## Release Process
 

docs/artifact_repositories/about.md docs/package_firewall/about.mddocs/artifact_repositories/about.md renamed to docs/package_firewall/about.md

@@ -1,6 +1,6 @@
-# Artifact Repositories
+# Package Firewalls
 
-Phylum for artifact repositories allows users to configure their artifact
+Phylum Package Firewalls allows users to configure their artifact
 repositories and/or package managers to block untrusted packages.
 
 ## How It Works

docs/artifact_repositories/api.md docs/package_firewall/api.mddocs/artifact_repositories/api.md renamed to docs/package_firewall/api.md

@@ -1,13 +1,13 @@
 # API
 
-This section provides additional instructions for usage of Phylum's Artifact
-Repository API. The full API is documented on [Swagger].
+This section provides additional instructions for usage of Phylum's Package
+Firewall API. The full API is documented on [Swagger].
 
-[Swagger]: https://swagger.phylum.io/?urls.primaryName=Artifact+Repository+API
+[Swagger]: https://swagger.phylum.io/?urls.primaryName=Package+Firewall+API
 
 ## Authentication
 
-The Artifact Repository API expects authentication in the basic auth format. The
+The Package Firewall API expects authentication in the basic auth format. The
 username is optional and provides context for which group should be used for the
 request. The group must either be the group name itself, for standalone groups,
 or the organization and group name combined using a `/`.
@@ -35,5 +35,5 @@ of the SHA256-HMAC of the response body, generated with the shared secret
 provided when registering the webhook. This checksum **must** be validated
 before accepting the authority of new webhook events.
 
-[register webhook endpoint]: https://swagger.phylum.io/?urls.primaryName=Artifact+Repository+API#/default/add_webhook
+[register webhook endpoint]: https://swagger.phylum.io/?urls.primaryName=Package+Firewall+API#/default/add_webhook
 [package check endpoint]: https://swagger.phylum.io/?urls.primaryName=API#/Organizations/organizations_group_packages_check