Update install docs with SP comments and backend state comments

[TechnicallyWilliams]

All Submissions:

---

• [YES] Have you followed the guidelines in our Contributing document?
• [YES] Have you added an explanation of what your changes do and why you'd like us to include them?
• [YES] I have updated the documentation accordingly.
• [NA] I have added tests to cover my changes.
• [NA] All new and existing tests passed.
• [NA] My code follows the code style of this project.
• [NA] I ran lint checks locally prior to submission.
• [YES] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

What is the current behavior?

---

Issue Number: [ #277 SP read request to Keyvault secrets fail with access denied ]

What is the new behavior?

---

• Documents will prevent fork and go users from copying state from source repo which results in a collision due to shared resources. It will also encourage usage of the same deployment SP for both source and fork and go repo.
• ADD_PAT_OWNER cli commands have been placed in their own file.
• An AZDO diagram for guidance on how to name the devops project and repo has been added to ADD_PAT_OWNER_CLI markdown.

Does this introduce a breaking change?

---

• [NO]

Any relevant logs, error output, etc?

---

(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Deployment errors due to using the same state but diffferent deployment SP from source repo.

Errors as a result of copying state file from source repo.

Deployment Error:
//
//...

Other information

---

[TechnicallyWilliams]

Descoping container validation. That issue can be found at #313 ([ Docs ] Document Steps for Container validation)

[ThePhen]

Good work @TechnicallyWilliams. This should have been accepted ages ago.