docs: proposal for enhancing scoped repository credentials

[blakepettersson]

Fixes #9581
Fixes #17897

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.
• Optional. My organization is added to USERS.md.
• Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

[yyzxw]

In my case, with appProject as the standard for multi-tenant isolation (a department, or a devops team, or a deployment environment), we added the same git repository to different AppProjects (even though the git repository credentials were the same).

For example, team A synchronizes repo/pathA (deploy application to dev) and Team B synchronizes repo/pathB(deploy application to prod).

So there are two possible scenarios:

The same repoUrl can be created multiple times, as long as their credential information is different
The same repoUrl can be bound to multiple AppProjects at the same time

[blakepettersson]

@yyzxw that is a reasonable request and would be supported by this proposal. The proposal intends to implement

The same repoUrl can be bound to multiple AppProjects at the same time

Whether the credentials are same or not would not matter; as long as they are in different projects that would still work.

[wanghong230]

As long as it has ensured backward compatibility, I think it is the proposal is quite legit to put into action.

[blakepettersson]

Thanks @wanghong230 and @christianh814! I clarified some sections in regards to backwards compatibility - the gist of it being that nothing will change unless there are multiple repo secrets sharing the same URL.

[jsoref]

Suggested change

	* If there are multiple repositories with the same URL and assuming the user is allowed to access them, then setting a
	* If there are multiple repositories with the same URL and assuming the user is allowed to access them, then setting a

[alexmt]

Thank you for resolving all comments @blakepettersson !