[FeatureRequest] Store build counters separately from version-controlled settings

Is your feature request related to a problem? Please describe.
ProjectSettings.json stores changing counters—such as the last build number and the total number of upload tasks started—alongside the Build Uploader configuration.
These counters are updated whenever I start a build or upload task, causing ProjectSettings.json to appear modified in version control even when none of the actual settings have changed. I want to keep my commits clean after running a build and avoid including unrelated counter changes.
I do not use these counters, but I do want to keep the Build Uploader settings under version control, so ignoring the entire file is not a suitable solution.

Describe the solution you'd like
Store frequently changing counters separately from the main ProjectSettings.json file. Ideally, they could be placed in a dedicated generated file so teams can choose whether to track it, while the actual project settings remain version-controlled.
Alternatively, an option to disable counter tracking or prevent these values from being updated would also solve the problem.

Describe alternatives you've considered
• Ignoring ProjectSettings.json, which would also exclude the actual shared configuration.
• Manually reverting only the counter changes before committing. This works and keeps commits clean, but doing it after every build is tedious.
• Committing the counter updates, which adds version-control noise without providing useful project history.

Additional context
I am using Build Uploader 3.3.0 with Unity 6000.3.24f1 on Windows 11. The project uses Unity Version Control (Plastic SCM), although the same issue would likely affect any version-control system.