smithy4sUpdateLSPConfig should render Maven Central if it's in resolvers

[kubukoz]

If you have any custom resolvers added in your build, then they'll be the only ones rendered into smithy-build.json. However, the default behavior for an empty resolver list is to use Maven Central (and probably m2 local), and using a different list removes that default.

It looks like our task deliberately doesn't write default resolvers, so as a result, adding a custom resolver means the LSP / smithy-cli won't use Maven Central anymore. I think we should be generating that repo, at least in situations where there are customer resolvers present.

[kubukoz]

Relevant code (filtering out Maven Central):

smithy4s/modules/mill-codegen-plugin/src/smithy4s/codegen/LSP.scala

Lines 48 to 50 in b25cefe

	.collect {
	case r: MavenRepository if !r.root.contains("repo1.maven.org") =>
	r.root

[Baccata]

Agreed

[kubukoz]

amended the title to be more precise - if the resolvers value doesn't contain maven central, we should still not render it (e.g. in cases you're working for an org that deliberately wants to avoid hitting MC)