Create matchVisibility config option within packageRules

[HonkingGoose]

Describe the proposed change(s).

Todos

• Add visibility field to RepoResult:

  renovate/lib/modules/platform/types.ts

  Lines 32 to 36 in 48e6aa4

  	export interface RepoResult {
  	defaultBranch: string;
  	isFork: boolean;
  	repoFingerprint: string;
  	}

• Add new matchVisibility option to packageRules

Context

@rarkins commented:

I was thinking that we should migrate from private/public repo concepts to "visibility" public/private (and I think "internal" is an additional one for GitHub). Then we could add a matchVisibility option to packageRules

And followed-up with:

On second look I don't see the terms private/public in platform code, so maybe I misremembered.

I think we could do this:

1. Add visibility field to RepoResult:

   renovate/lib/modules/platform/types.ts

   Lines 32 to 36 in 48e6aa4

   	export interface RepoResult {
   	defaultBranch: string;
   	isFork: boolean;
   	repoFingerprint: string;
   	}

2. Add new matchVisibility option to packageRules

Related discussion

• Is there a way to have public and non-public repos distinguish configuration, without using multiple presets? #29746