nacos-client, the default value of namespace set for naming and config is inconsistent, resulting in permission authentication failure

[Maijh97]

Describe the bug

1）nacos-client
naming进行服务注册，当namespace没有指定，会默认为public，参考代码为: com.alibaba.nacos.client.naming.utils.InitUtils#initNamespaceForNaming
config进行获取配置，当namespace没有指定，会默认为空字符 "", 参考代码为:
com.alibaba.nacos.client.utils.ParamUtil#parseNamespace

2）控制台新建权限
如果分配的资源为public，这时候数据表permissions中的resource字段就会为 :*:* ，如果是分配其它自定义命名空间的资源就会为 07ba088a-4782-468e-80cc-ee758beab327:*:*

3）com.alibaba.nacos.core.auth.AuthFilter权限拦截校验
如果是config请求，组装的权限resource 为 :DEFAULT_GROUP:config/service-gateway
如果是naming请求，组装的权限resource为 public:DEFAULT_GROUP:naming/service-gateway
导致使用java.util.regex.Pattern#matches方法匹配权限, naming请求权限会不足
伪代码:

a = ":*:*";
b = "public:DEFAULT_GROUP:naming/service-gateway";  // naming
c = ":DEFAULT_GROUP:config/service-gateway";  // config

Pattern.matches(a, b); false
Pattern.matches(a, c); true

Expected behavior

希望能统一nacos-client的namespace默认值；
比如config在namespace没有指定的情况下应该也默认为public
在新建资源的时候，当选择的资源为public的时候， resource应为： public:*:*

Acutally behavior

How to Reproduce

Desktop (please complete the following information):

• OS: [e.g. Centos]
• Version [e.g. nacos-server 1.3.1, nacos-client 1.3.1]
• Module [e.g. naming/config]
• SDK [e.g. original, spring-cloud-alibaba-nacos, dubbo]

Additional context
Add any other context about the problem here.

[KomachiSion]

is related with #3524 ?

[Maijh97]

is related with #3524 ?

yes

[Maijh97]

Also related to the #2620 issue