Summary

Closes #2392

I've re-enabled the maturity filter for comments here, in the same style as we handle it in activities.

Steps to test

Note: if you are the owner, your text is in the show state by default.

1. Login.
2. post a non-mature comment on a post.
3. post a mature comment.
4. Repeat steps 2 and 3, nesting into the comment tree so that you have 3 tiers of mature and non-mature comments.
5. Refresh, the posts, they should all be visible as you are the logged-in user.
6. You should be able to click on the red E icon to blur mature the posts.
7. Copy the link to the post.

Then,

1. Log out
2. Go to the post you made above.
3. Check the mature text is all blurred.
4. Click on the text, not the E button to ensure it gets rid of the blur,
5. Click the text again, it should do nothing.
6. Click the button again, it should re-blur.
7. Cycle the button on and off to check it works properly.

Estimated Regression Scope

This change effects comments.

The html-template changes should be self-contained; I don't think they'd affect anything outside of their lines of code by themselves, the only bit of code that really touched anything is in the ngOnInit(), where I check the users guid, and set the content to show if they are the owner of the comment. So, as a worst-case scenario, maybe it would show by default for everybody.

added scoped labels

Aware of this one, deploying to sandbox to write the E2E tests.