Update "WALLY Information.docx" Document in 'Dev Chat'

**Describe the task**
Update "WALLY Information.docx" Document in 'Dev Chat'

**Purpose**
Not all information and tips need to be documented in a public facing repo. But with developers cycling through Sustainment team its valuable to keep this information for the next generation of developers to consume when working in these spaces

**Acceptance Criteria**
- [ ] Information Cleaned up, Updated and Added to in Document
- [ ] Headers used appropriately
- [ ] Table of contents updated (it's a single button press)

**Additional context**
- You can add tips involving setups, weird nuances, or advice if future tickets may impact an area you worked on
- GWELLS currently has a pretty up to date one, for reference
- Wally hasn't had its changes in review in a long time, which means there has a been a long time without developers working in that space. There is a much higher chance all knowledge in that application can be graduated out of the sustainment team before work resumes

Locate the "WALLY Information.docx" document in Dev Chat and compare it with the referenced GWELLS document. Review the existing content for outdated or missing setup tips, nuances, and advice, then clean up the information, apply appropriate headers, and update the table of contents. Done means the document is current and useful to future sustainment developers.

Written by the indexing model from the issue text.