Fix JMX Metrics export error

[LiYangSir]

…el/issues/2989

Describe what this PR does / why we need it

Fix JMX Metrics export error, Before registering, first escape the special characters [*, ?, ", \n, =, :] in the resource name.

1. Solve the problem of "cannot add mbean for pattern name" exception thrown during registration, eg [*, ?].
2. Solve the problem of "invalid character in value part of property" exception when creating ObjectName, eg[", \n, =, :]

Does this pull request fix one issue?

Fixes #2989

Describe how you did it

Escape the resourceName by call "quote" method before creating the registration, escape if the resource name contains special characters, otherwise do nothing.

Describe how to verify it

By installing the new jar package locally and retesting the resource name containing 6 special characters, there is no abnormality in the Record log, and there is no abnormality in the Mbean display.

try (Entry entry = SphU.entry("*HelloWorld")) {
    // Your business logic here.
    System.out.println("hello world");
} catch (BlockException e) {
    // Handle rejected request.
}

Special notes for reviews

None

[CLAassistant]

All committers have signed the CLA.

[sczyh30]

cc @xiangtianyu @garroshh @BlueSodaWater for review

[garroshh]

LGTM

notice：for those special characters，metrics lable value will add “” and \, but that's right.
when i visit http://localhost:8092/*version with special character in browser or visit http://localhost:8092/\*version with special character in cli，generate the metric like fllow pic：

[LiYangSir]

@garroshh Added string quote and escapes for special character to resource name when there are special characters

[sczyh30]

LGTM

[garroshh]

LGTM

[sczyh30]

Thanks for contributing and look forward to more! 👍