[Advancement] Add shared project lockfiles for team CLI config subsets

[Nanle-code]

Objective

Allow teams to commit a non-secret project lockfile for shared networks, templates, and quality gates.

Target area

config system

Context

Shared non-secret settings reduce “works on my machine” issues for Wave teams.

Requirements

• Separate secrets from shareable project config
• complement user-level config with project overrides
• Validate schema on load

Acceptance criteria

• Project lockfile is detected and applied
• Secrets remain excluded by schema
• Docs describe team workflow

Pull request merge requirements

Pull requests that resolve this issue must not be merged until all of the following are true:

1. All required CI checks are green on the latest commit of the PR (build, tests, lint/format, and any workflow jobs required by branch protection).
2. The branch has no merge conflicts with the target branch (master / default), and a clean merge or rebase is possible without unresolved conflicts.
3. Review feedback is addressed, and the change remains focused on this issue’s acceptance criteria.

Contributors should run the local CI-equivalent checks before opening or updating the PR (see CI_ENFORCEMENT.md and CONTRIBUTING.md).

[Tboy123-emm]

@Tboy123-emm has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello please I'd like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Tboy123-emm to this issue.