Bring CE->EE source upgrade instructions up to par

What does this MR do?

The source CE to EE upgrade instructions were out of date. This MR brings it up to par with the upgrading from source instructions.

See: https://gitlab.com/gitlab-org/gitlab/blob/ef771a90892ef5616787c33e3d15589660a81517/doc/update/upgrading_from_ce_to_ee.md

vs

https://gitlab.com/gitlab-org/gitlab/blob/1b3d3ccd449ae539f1debb7a11f29d0242c5ed68/doc/update/upgrading_from_source.md

Closes https://gitlab.com/gitlab-com/support/docs/issues/45

Related issues

This was reported by a customer (Zendesk, internal use only) who found UI elements missing as their assets were not recompiled.

Author's checklist

• Follow the Documentation Guidelines and Style Guide.
• If applicable, update the permissions table.
• Link docs to and from the higher-level index page, plus other related docs where helpful.
• Apply the documentation label.

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

• Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

• Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
2. Ensure a release milestone is set.
3. If there has not been a technical writer review, create an issue for one using the Doc Review template.