pkg/path, tool/file: no error when '**' used as part of glob

[myitcv]

What version of CUE are you using (cue version)?

$ cue version
cue version v0.0.0-20240723144244-32013a749daf

go version go1.22.3
      -buildmode exe
       -compiler gc
     CGO_ENABLED 1
          GOARCH arm64
            GOOS linux
             vcs git
    vcs.revision 32013a749dafea2fc7c60fb7d7f0c7e5706d60ba
        vcs.time 2024-07-23T14:42:44Z
    vcs.modified false
cue.lang.version v0.10.0

Does this issue reproduce with the latest release?

Yes

What did you do?

! exec cue cmd x
stderr 'cannot use ** in call to path\.Match'
stderr 'cannot use ** in call to file\.Glob'

-- x_tool.cue --
package x

import (
	"path"
	"strings"

	"tool/cli"
	"tool/file"
)

command: x: {
	print: cli.Print & {
		let res = path.Match("**/blah.json", "blah.json", "unix")
		text: """
			path.Match("**/blah.json", "blah.json", "unix") = \(res)
			"""
	}
	glob: file.Glob & {
		glob: "**/blah.json"
		files: [...string]
	}
	globResult: cli.Print & {
		text: """
		file.Glob(glob: "**/blah.json") => \(strings.Join(glob.files, ", "))
		"""
	}
}

What did you expect to see?

Passing test, for some variation of the error message.

What did you see instead?

> ! exec cue cmd x
[stdout]
path.Match("**/blah.json", "blah.json", "unix") = false
file.Glob(glob: "**/blah.json") =>
FAIL: /tmp/testscript3699288200/repro.txtar/script.txtar:1: unexpected command success

The main motivation for making the use of ** an error in these two situations is to achieve consistency with the embed proposal. If we consistently do not allow ** anywhere there is "glob"-like behaviour then:

• Nobody can be relying on it accidentally to do something it doesn't know about
• We can later allow the use of ** in any/all of these places as we introduce support for it.