METRON-2084 Add documentation notice for MacOS Mojave users for new security permissions

[mmiklavc]

Contributor Comments

https://issues.apache.org/jira/browse/METRON-2084

Doc update that addresses a common developer issue with getting full dev working on Mac OS Mojave. I verified the site-book looks correct and the referenced link works as intended.

Pull Request Checklist

For all changes:

• Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
• Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
• Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

• n/a Have you included steps to reproduce the behavior or problem that is being changed or addressed?

• n/a Have you included steps or a guide to how the change may be verified and tested manually?

• n/a Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:

  mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh 
  

• n/a Have you written or updated unit tests and or integration tests to verify your changes?

• n/a If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

• n/a Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

• Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:

  cd site-book
  mvn site
  

• n/a Have you ensured that any documentation diagrams have been updated, along with their source files, using draw.io? See Metron Development Guidelines for instructions.

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

[anandsubbu]

+1 by inspection. Thanks @mmiklavc for the note, this is helpful indeed!

[mmiklavc]

Looks like the unrelated test failure is the same as the one reported here - https://issues.apache.org/jira/browse/METRON-2166. I'm looking into it now so we can get master back on track.