Design Review: Analyst view of org domain requests

[katypies]

Issue Description

We're implementing a new version of the domain request workflow for the organization model, since we'll have some common information that's known for users who are requesting from within an organization. Additionally, we may have some added information that is being derived from the organization or that we're requesting in the flow. This ticket is to review Django Admin page(s) that Analysts have access to, for domain requests from someone within an organization. A few key things we know we will want to highlight or ensure is clear for Analysts:

1. Because a portfolio exists, we know that the organization is eligible for a .gov domain.
2. Within the portfolio, we know who the Senior Official is, and are already storing that for the organization. This should not need to be validated or verified.
3. The person making the request is authorized to do so on behalf of the organization. We don't need to validate that they are who they say they are, or that they're authorized to make the request. That is/will be presumed because of their addition to the portfolio organization.

In addition to making these clear, Design should review any added tables/fields to ensure they're displayed logically and consistently with other patterns on the page and are appropriately contextualized for an Analyst viewing a domain request.

Acceptance Criteria

• [ ] Design reviews the Domain Requests page (/admin/registrar/domainrequest/) and the individual Domain Request page (/admin/registrar/domainrequest/{ID}/change/)
• [ ] Ensure that the data presented makes sense and is appropriately labeled and/or contextualized
• [ ] Ensure that the considerations and known information noted above is presented clearly to analysts.
• [ ] Document any changes needed or new additions in a document, including with screenshots so it is easy to follow
• [ ] Discuss changes with dev and determine which are small enough to be done as part of this ticket
• [ ] Work with dev to create new tickets for larger changes

Additional Context

Working with dev: Dev effort on this shouldn't be more than a "2" (2 full work days).

Dev is responsible for answering questions from design, making minor changes (such as those that we would normally make on a PR). Anything that would take more than 4 hours to complete alone should be it's own ticket. If the amount of changes desired would result in the dev spending more than a full day on it, make a dev ticket for items where reasonable (communicate with Alysia).

Links to other issues

There are several related issues in this milestone, but it's anticipated that this should be viewed holistically rather than in the context of those changes to confirm that the information presented makes sense and can be actioned for Analysts.

[github-actions[bot]]

cc/ @Katherine-Osos — adding you to this design-review issue!

[katypies]

Added refinement to be sure we get this pointed, and ensure dev + design are clear on the outcomes needed.