`Failed to process Gradle file` shouldn't include full resolved `config`

[jamietanna]

Noticed this on a repo:

DEBUG: Failed to process Gradle file
{
  "err": {
    "message": "Expected token registryUrl not found",
    "stack": "Error: Expected token registryUrl not found\n    at ..."
  },
  "config": {
    "mode": "full",
    "detectGlobalManagerConfig": false,
    "detectHostRulesFromEnv": false,
...

I don't think this should include the full config object

(There are some other places we do this too, and IMO, it's fairly noisy when really the repo config is all we need to log)

[Churro]

"Expected token ... not found" should never happen - it's a bug in the gradle parsing directives.

The underlying problem is that qMavenArtifactRegistry puts no hard constraint on registryUrl being set:

renovate/lib/modules/manager/gradle/parser/registry-urls.ts

Lines 131 to 144 in 0b99aa1

	search: q.alt(
	q
	.sym<Ctx>('name')
	.opt(q.op('='))
	.join(qValueMatcher)
	.handler((ctx) => storeInTokenMap(ctx, 'name')),
	q.sym<Ctx>('url').opt(q.op('=')).join(qUri),
	q.sym<Ctx>('setUrl').tree({
	maxDepth: 1,
	startsWith: '(',
	endsWith: ')',
	search: q.begin<Ctx>().join(qUri).end(),
	}),
	qRegistryContent,

At this point, this is challenging to achieve since we don't know in which sequence n a URL occurs within a maven { ... } block.