feat(ui5-tooling-modules): make JSDoc visibility configurable

[H4ze]

No description provided.

[petermuessig]

@H4ze @Thodd with that approach we can at least control either: @privateand @public but what about adding @experimental + eventuall a text and @ui5-restricted + eventuall a text ?

Maybe for that we add two more pluginOptions:

• isExperimental with type boolean|string (boolean means @experimental tag added without text and with a string value you can define the text to set?)
• isUI5Restricted with type boolean|string (boolean means @ui5-restricted tag added without text and with a string value you can define the text to set?)

WDYT?

[H4ze]

@H4ze @Thodd with that approach we can at least control either: @privateand @public but what about adding @experimental + eventuall a text and @ui5-restricted + eventuall a text ?

Maybe for that we add two more pluginOptions:

• isExperimental with type boolean|string (boolean means @experimental tag added without text and with a string value you can define the text to set?)
• isUI5Restricted with type boolean|string (boolean means @ui5-restricted tag added without text and with a string value you can define the text to set?)

WDYT?

Hmm I'm not sure about the use-cases.
experimental would also already work just without additional text. Is there really an additional text needed?
For ui5-restricted I thought about visibilityJSDoc: [my.lib.a, my.lib.b] in order to add @private and @ui5-restricted my.lib.a, my.lib.b.

[codeworrior]

Since 1.139, @experimental should no longer be used, use @ui5-experimental-since instead (which does not support a text, btw). See "Guidelines+for+experimental+APIs" in the UI wiki space.

[petermuessig]

LGTM - let's merge this one for now