Rename components outside of common module that have misleading names

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->

To eliminate needless guesswork, component names should clearly indicate what the component does and how it is used. 

This is _mostly_ for changing the names of things that are the most misleading or don't reflect component hierarchy (as opposed to formatting everything so it fits with BEM rules). 

The list of names to change is: 
 
- [x] m-shadowboxLayout > data tab
- [x] m-concertColors__modal > (name shouldn't depend on an image it formerly used ) photo banner modal?
- [x] m-formToast > (also used outside of forms) m-toast...should probably also do the related service
- [x] m-reports__marketing > (this is actually the content policy aux page) content policy?
- [x] m-wireCreator__marketingBlock > (not clear what is being marketed) m-wireCreator__upgradeBlock
- [x] m-composer__preview > m-composer__previewWrapper
- [x] m-composerRichEmbedPreview > m-composerPreview--richEmbed
- [x] m-composerRemindPreview > m-composerPreview--quote (it's a QUOTE not a remind)
- [x] m-composerAttachmentPreview > m-composerPreview--attachment
- [x] minds-groups-join-button (more than just join) > m-group__membershipButton
- [x] m-homepagecontainer > m-homepageContainer
- [x] minds-form-login > looks too ancient... change to m-loginForm
- [x] minds-form-register > m-registerForm


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
- [x] Change names of list above
- [x] Where appropriate, also update css classes to match the component names
- [x] If changing names of `.scss` files, go ahead and convert to `.ng.scss` as needed

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
Visual check of the affected components

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
N/A

## Personas

<!---
Who does this user impact and why (optional)
--->
Developers

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
None

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Affected components look/act the same but are easier to use
- [ ] Update spreadsheet to reflect new names

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Rename components outside of common module that have misleading names

Story points: 1.0