Template Loader: Use glob constant instead of numeric value.

[epiqueras]

Fixes #18876

Description

This PR changes the calls to glob in the template loader to use the constant GLOB_NOSORT instead of the literal 1 which seems to have been causing issues in certain environments.

How has this been tested?

It was verified that template loading still works as expected.

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR. .

[aduth]

Can you explain what's meant to be accomplished with this flag?

And what was meant to be accomplished with the previous value? (since GLOB_NOSORT evaluates to 32, a different behavior from what existed previously)

[epiqueras]

I thought the constants were 0 indexed and intended to use GLOB_NOSORT to be more efficient since we don't need to sort the results here.

[aduth]

intended to use GLOB_NOSORT to be more efficient since we don't need to sort the results here.

Does it make a measurable difference?

If I find myself questioning why it exists today, I think it would be a fair assumption that it might catch the attention of future maintainers as well, as to why it needs to exist.

At the very least, if we keep it, can we add an inline comment explaining its purpose for the benefit of those who work with this code in the future?

[epiqueras]

I don't think the minimal performance difference warrants the potential for confusion so I've removed them.

[johnbillion]

+1 for removal. The performance benefit here will be negligible.