Your project’s Administration → Background Tasks → [ row dot menu] → Show SonarScanner Context reflects the values that were actually used during analysis.
The docs give you the precedence of parameters set in different places. Basically, those set closer to the actual analysis command take precedence.
Now to the question of where the overwrite is coming from. Since you’re using automatic analysis, the override can’t be on the command line. Can you double-check your .sonarcloud.properties file to make sure the inclusions parameter isn’t set a second time farther down in the file?
For Java projects, the automatic analysis doesn’t support changing sonar.sources and sonar.inclusions properties. So, we have some undocumented limitations for automatic analysis for Java projects. We should either update our documents or support changing the properties written in our docs soon.
What you can do for now to reduce the amount of code to be analyzed is to exclude files in the UI under Your Organization > Your Project > Administration - General Settings > Analysis Scope > Files. Please note that automatic analysis only takes the exclusion configuration in the UI into account but not in the .sonarcloud.properties file for now.