see https://github.com/cnpm/unpkg-white-list
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Introduced a new configuration option `enableSyncUnpkgFilesWhiteList`
to enhance package version file synchronization.
- **Improvements**
- Enhanced logging in package version file operations for better
traceability.
- Simplified file redirection logic for improved performance and
readability.
- **Tests**
- Added test cases for the new `enableSyncUnpkgFilesWhiteList`
configuration to ensure reliability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
> closes#574 Fixed the issue where custom tags in publishConfig
prevented the default latest tag.
* 🧶 Modified the `savePackageVersion` API, automatically add latest tag
if no latest tag.
* 🧶 The publish tag parameter has been changed to tags, triggering
corresponding events in batches.
* ♻️ No changes to the package synchronization process.
------
> closes#574 修复 publishConfig 中自定义 tag，导致 latest tag 未设置的问题
* 🧶 修改 savePackageVersion 接口，如果当前包未配置 latest tag，则自动补全
* 🧶 publish tag 参数改为 tags，对应事件分批触发
* ♻️ 包同步流程不做修改
> Attempted to apply the `noImplicitAny`, parameter types should be
specified unless any is manually declared.
* 🐞 Fixed an issue in bugVersionAdvice where AbbreviatedManifest was
being set abnormally.
* 🤖 Added index.d.ts to store declarations for dependencies without
types.
* 🤔 skipLibCheck has no effect on leoric for now, so it cannot be
enabled temporarily.
--------
> 尝试应用 `noImplicitAny` 配置，除非手动声明 any，否则需要指定参数类型
* 🐞 修复 bugVersionAdvice 中，AbbreviatedManifest 设置异常
* 🤖 添加 index.d.ts 存放无类型依赖声明
* 🤔 skipLibCheck 对 leoric 失效，暂时无法开启
> When concurrently executing packet sending, there is a possibility of
version overwrite
* 🧶 Add `usingLock` logic to the publish interface to handle concurrent
execution, which will prevent version overwrite
* 🔨 Modify usingLock to include a return value indicating the success of
lock creation
------
> 并发执行发包时，可能出现版本覆盖问题
1. 🧶 在发布接口中，添加 usingLock 逻辑，包同步场景不涉及
2. 🔨 `usingLock` 添加返回值，标记是否创建锁成功
> Validate the manifest and tarball info to prevent contamination during
consumption, closes#542.
1. 🔨 Added the "strictValidateTarballPkg" mode to enable validation,
only applicable to the slef registry scenario.
2. 🧶 When the configuration is enabled, validate the relevant fields
during publishing, currently only validating the fields affecting
consumption.
3. ♻️ No corrective actions will be taken for existing scenario data.
-----
> 发布时校验 manifest 和 tarball 字段是否陪陪，防止消费时被污染 closes#542
1. 🔨 新增 strictValidateTarballPkg 配置，仅对在发布当前 registry 场景下生效
2. 🧶 配置开启时，发布时校验相关字段，目前仅校验影响消费相关字段
3. ♻️ 存量场景数据不做订正处理
> Add a private field, _source_registry_name in the version manifest.
* 🧶 Add related types for PackageManifestType and adjust relevant unit
tests.
* 🤖 Update the workflow trigger.
* ♻️ No compensation will be made for the _source_registry_name field in
the existing packageVersion.
-------
> 在 version manifest 中新增私有字段，_source_registry_name 用于标记
* 🧶 新增 PackageManifestType 相关类型，并调整相关单测
* 🤖 调整 workflow 触发时机，不限制 target 分支
* ♻️ 存量 packageVersion 内 _source_registry_name 不做补偿
> Support for migrating packages into current registry
1. 🆕 Add `ensureSelfRegistry` method to initialize the current
configuration to the DB
2. 🧹 Add displayName to hide userPrefix info
3. 🧶 Uniformly determine publish access with `checkPublishAccess` and
`ensurePublishAccess`
--------------
> 支持将包迁移至当前 registry，避免不再进行包同步
1. 🆕 `ensureSelfRegistry` 方法，将当前配置初始化至 DB
2. 🧹 添加 displayName，外部不再展示 userPrefix 信息
3. 🧶 通过 checkPublishAccess 及 ensurePublishAccess 统一判断发布权限
