scripts: avoid pointless LICENSE churn

I was wondering why a bot decided to force-push a commit to a PR of
mine. It turns out the script responsible for generating the LICENSE
file is not deterministic, so depending on random file system layout
we can end up regenerating the LICENSE without any actual change. For
example:

$ diff -u <(git show baf2067~1:LICENSE | sort) <(git show baf2067:LICENSE | sort)

shows that baf2067 didn't provide any change at all in the actual
contents, yet

$ git show --stat baf2067
commit baf2067
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Date:   Wed Jan 22 21:42:44 2025 +0000

    Auto-update LICENSE file with current recipe licenses

 LICENSE | 256 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------------------------------
 1 file changed, 128 insertions(+), 128 deletions(-)

Author: ravi-prevas

scripts/generate-license-file

@@ -1,13 +1,15 @@
 #!/bin/bash
 
+export LC_ALL=C
+
 # Create or clear the LICENSE file
 echo "# License Information" > LICENSE
 echo "" >> LICENSE
 echo "This file lists all licenses used by recipes in the meta-freescale layer." >> LICENSE
 echo "" >> LICENSE
 
 # Find all .bb and .inc files and extract license information
-find . -type f \( -name "*.bb" -o -name "*.inc" \) | while read -r file; do
+find . -type f \( -name "*.bb" -o -name "*.inc" \) | sort | while read -r file; do
     # Extract the license line from each recipe file, if it exists
     license_line=$(grep -i "^LICENSE" "$file")
     if [ -n "$license_line" ]; then