fix: a typo in _OBSOLETE_MANUAL_BUILD_ORDER everywhere

[MojtabaHs]

I’ve resolved the issue throughout the codebase. However, since it involves a public property, it might be wise to introduce an alias using @available to enable automatic renaming.

Let me know your thoughts.

Also, please remember to run the @swift-ci test.

[jakepetroules]

However, since it involves a public property, it might be wise to introduce an alias using @available to enable automatic renaming.

This is underscored and undocumented, it's not meant to be a public interface.

[jakepetroules]

@swift-ci test

[mirza-garibovic]

Can you please update the title and description of this PR to specify that it's a typo fix just like in your commit message? And do so for PRs going forward.

[neonichu]

I agree with @mirza-garibovic on the title, but otherwise this looks good.

[neonichu]

@swift-ci test

[MojtabaHs]

@mirza-garibovic thank you for the suggestion! Title has been updated as requested.

I will try to reuse the PR title with the commit messages if they reflect similar changes. However, most of the time PRs include multiple changes with several commits (to facilitate easier reviews and any back-and-forth updates) and I need to summarizes the overall changes.

I usually try to cover these in the summary, short and minimally:

• What Module/Feature changed? e.g. [SWBCore]
• Why I changed this? e.g to Enhance or refactor or extending code coverage or fix or etc.
• What part of the Module/Feature changed? e.g. Settings or PIFGenerationModel or etc.
• What was the overall type of changes? e.g inline documentation, tests, warning, properties, etc.

If there are any guidelines to follow, please let me know. I would be happy to review them.

[mirza-garibovic]

@MojtabaHs thanks! Your thinking is good but summaries should be specific about the nature of the enhancement.