fix: removed a warning that falsely warns that getPublicPath is ignored

[vergilfromadyen]

It looks like the warning was introduced in this commit.
getPublicPath was restored a day later in this commit, but the warning is still in the code.

Nowadays publicPath and getPublicPath are still in the code, so these options don't appear to actually be ignored.

[gioboa]

Thanks for your help @vergilfromadyen 👏

[gioboa]

LGTM, thanks @vergilfromadyen

The warning is to highlight that "experimental.renderBuiltUrl" is used but right now we are still using getPublicPath 🤔

[vergilfromadyen]

Thanks @gioboa for merging this. Any chance we could get a patch release so I can un-spam my console? :)

Also, a migration example would be nice when this actually ends up being removed.
My case is that I'm using it as

getPublicPath: `function() {
  const url = new URL(document.baseURI);
  return document.baseURI + 'some-subpath' + url.pathname + '${domain}/'; // domain is declared elsewhere in the file
}`

I couldn't replicate that with experimental.renderBuiltUrl, granted I didn't really spend any meaningful amount of time trying to and opted to remove the warning upstream.

[gioboa]

Any chance we could get a patch release so I can un-spam my console? :)

There we go 1.9.1