Toogle labels option

[Palt]

Description

Added toggles to the SettingsMenu with the options to toggle the labels of Nodes and Edges.

Motivation and Context

This PR addresses: #431

These changes will allow a user to toggle the labels and make it easier to hide potential sensitive data before taking a screenshot.

How Has This Been Tested?

Locally tested manually and using existing tests.

Screenshots (optional):

Types of changes

• New feature (non-breaking change which adds functionality)

Checklist:

• I have met the contributing prerequisites
  • Assigned myself to this PR
  • Added the appropriate labels
  • Associated an issue: Issues and Pull Requests README #672
  • Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing
• I have ensured that related documentation is up-to-date
  • Open API docs
  • Code comments (GoDocs / JSDocs)
• I have followed proper test practices
  • Added/updated tests to cover my changes
  • All new and existing tests passed

[StephenHinck]

Good morning, @Palt, and thank you for another contribution! I have some functional feedback on your PR before I ask our Engineering team to review the code.

• The "Explore" portion of the product is one subset of BloodHound's functionality. As such, changes that impact only that portion of the application must live within the page and not at a global level. Our UX designer has provided the following mockup for the expected behavior of this function within the product within the graph context specifically (specifically the menu in the bottom-left corner):
  
• The graph elements should maintain a static position regardless of whether labels are displayed or hidden; the view should not reset when toggling the label elements on and off.
• We would like to include options to show or hide all labels quickly.

I appreciate the effort you've put into this, and I recognize this is a decent bit of rework on the changes you have already made. We do have some upcoming work planned for our team, where they can help take this across the line if you'd rather not rework!

On a related note, I would love to send you a swag package to show our gratitude for your contributions to the product. If you can send me an email at shinck (AT) specterops (DOT) io with your shipping address, I'll get that on its way!

[Palt]

Hi @StephenHinck, and thank you for great feedback!

I’m happy to be able to contribute when I can as this is an awesome tool that I use quite a lot.

Reading through what you’ve written it is as you say, this is not the way to implement it. I’ll blame it on my lack of understanding of the project and will continue digging a bit deeper into it to get a better grasp on it.

I’ll see what I can do to see if I can implement the needed changes to get it to a state where you can agree with it.

Regarding Swag: Thank you! I’ve sent you an email.

[Palt]

I've re-done the PR and would say that it now aligns with what you described @StephenHinck. It is now a smaller change and far less complex from previous solution.

Hope it is what you are looking for.

[elikmiller]

@StephenHinck are the updates from @Palt what you are looking for? If so we can start getting this code reviewed.

[StephenHinck]

@StephenHinck are the updates from @Palt what you are looking for? If so we can start getting this code reviewed.

From a functional perspective, this matches our AC. The ticket is up at BED-4613 internally!