Website Build Scripts Path Confusion and Filesystem Watching

[aj-stein-nist]

Describe the bug

I determined this yesterday when completing a review for #1089, but the run script had some minor pathing issues that load somewhat confusing mounts of /oscal for the source code and remounting the sub-directory of docs as /docs within the container. Additionally, the container does not watch for local changes (hugo --watch ...) so reloading the server manually slows down the development and review flow.

Who is the bug affecting?

NIST OSCAL Developers, primarily those reviewing the website changes during review before merge and publication at pages.nist.gov/OSCAL.

What is affected by this bug?

An ergonomic experience for testing website content, using the same docker-compose mounts and harness for all the respective images for build and local web dev testing.

When does this occur?

Frequently

How do we replicate the issue?

{What are the steps to reproduce the behavior?

1. Build and run the container for local builds and testing (cd /path/to/oscal/build && docker-compose build && docker-compose up -d)
2. Build and run the local web testing container (`cd /path/to/oscal/docs && docker-compose build && docker-compose up -d)
3. Observe mount confusion and the lack of reload content as source file changes are made in source tree

Expected behavior (i.e. solution)

A more ergonomic dev, build, test cycle