Opt in to Gradle wrapper use if present, or custom option if not

### Description

The current Gradle config settings (NB28) allow one of:

- Prefer to use Gradle Wrapper that Comes with the Project
- Custom

Given that it inevitably/understandably takes time for each version of NB to support new features, it would be useful to have the option to use Gradle Wrapper if present, with a custom fallback otherwise (instead of fallback to the bundled Gradle version).

### Use case/motivation

Trying to improve Gradle version selection for different projects with/without use of wrapper.

### Related issues

_No response_

### Are you willing to submit a pull request?

No

Start by locating the Gradle configuration settings described as NB28 and the existing choices for the project wrapper and custom Gradle version. Trace how the selected Gradle version is resolved when a wrapper is present or absent. Done means a project can opt into wrapper use with a custom fallback instead of the bundled version, with the relevant behavior covered by tests.

Written by the indexing model from the issue text.