Descriptive text needs to be associated with the field not at the top of the blade

**Problem:** Descriptive text needs to be associated with the field not at the top of the blade.

**Why is this an issue?**

- Service teams have asked that we be more descriptive in providing guidance as it relates to the action, we are asking them to complete. Most new service teams will not know what a hero scenario or core concept document is yet. We need to provide a helpful description and a link to where they can find additional information and examples.
- We should clearly state if a field is optional or required, not have a statement at the top that a user could overlook.

**Requirement:**
- Discovered in Information Meeting but should apply to UI in all of the meetings.
- Remove this text which is not grammatically correct - _NOTE: This meeting documents to be submitted before the meeting starts. Please review the list of requirements [here ](https://aka.ms/azsdk/onboarding/informational)before picking a date. Failure to provide this documentation before the meeting will result in automatic cancellation of this meeting. _
- Instead add hover text or ? by each field that briefly explains the document and provides link to an example.
- For core concepts indicate that the field are optional - core concepts doc link (optional). Hover text should state "Completion of core concepts is optional for this meeting. . "
- For hero scenario link indicate that the field is optional - hero scenario link (optional). Hover text should state "Completion of initial hero scenarios is optional for this meeting. . "

No files or tests are named; start by locating the Information Meeting blade and the corresponding UI for the other meeting types. Review the existing top-level descriptive text and the core concepts and hero scenario fields, then verify that each field has optionality guidance, hover help, and the requested links without the old message.

Written by the indexing model from the issue text.