docs(config-overview.md): explain order of operations for final config

[KUGA2]

Changes

• Add possible options for global config
• State that the order is the precedence order
• Fix order

Context

#32598

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository
• None of that. Its documentation only.

[rarkins]

I still see this "rich" diff:

Is the diff wrong?

[HonkingGoose]

I don't know how this looks in the published docs... 😞

The published docs use a Python Markdown variant. But the rich diff on GitHub assumes the input is GitHub Flavored Markdown.

I remember us having problems with list formatting as Python Markdown uses 4 spaces. But GitHub-flavored markdown uses different conventions for some list types.

[rarkins]

Maybe should we use a) b) c) instead?

[HonkingGoose]

Maybe should we use a) b) c) instead?

Sounds good!

It will probably not fix the problem of the layout, but it's easier to read and remember.

A number and a letter seems better than a number and then a slightly different number.

[HonkingGoose]

Suggested change

	When Renovate runs on a repository, the final config used is derived from the following config locations. The below is the order of precedence:
	Each time Renovate runs on a repository it reads the configuration files listed below and creates a final config.
	This final config describes what Renovate will do during its run.
	The final config is internal to Renovate, and is _not_ saved or cached for a later run.
	But you can always find the final config in Renovate's logs.
	Renovate reads the configuration files in this order (from from top to bottom):

I think we should explain that:

• the final config is internal to Renovate
• and that Renovate does not save/cache the final config for later (I think?)
• Renovate puts the final config in the log output

Plus I'm rewriting bits we already had. 🙂

[rarkins]

This is technically true but might confuse someone. If repositoryCache is enabled, then Renovate will cache the repository config, using the default branch SHA as cache key. However the "final" config is derived from all the configs together and it is always recalculated/non-cached