Correct config usage for generate-test-project and generate-sample-project

[welovej]

Description

config: generate-test-project's default value is false, but generate-sample-project's default value is true. Before this PR, If both used default value, judegment about generate-test-project is actually depend on generate-sample-project.

Checklist

To ensure a quick review and merge, please ensure:

• The PR has a understandable title and description explaining the why and what.
• The PR is opened in draft if not ready for review yet.
  • If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review
• The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

• Build is completely green
  • Submissions with test failures require tracking issue and approval of a CODEOWNER
• At least one +1 review by a CODEOWNER
• All -1 reviews are confirmed resolved by the reviewer
  • Override/Marking reviews stale must be discussed with CODEOWNERS first

[live1206]

config: generate-test-project's default value is false, but generate-sample-project's default value is true. Before this PR, If both used default value, judegment about generate-test-project is actually depend on generate-sample-project.

Should generate-test-project be default as true as well? Before this PR, the current behavior of generate-test-project is default as true.

[pshao25]

I don't think it is correct behavior. It changes DPG's behavior.