feat: more general definition of changes requiring attention in tooltip (#34)

Co-authored-by: Iurii Golovinskii <[email protected]>

Author: iurii-golovinskii

src/test-data/shared/messages.ts

@@ -1,11 +1,7 @@
 export const TOOLTIP_SEVERITY_MSG = {
   breaking: 'Breaking change is a change that breaks backward compatibility with the previous version of API. For example, deleting an operation, adding a required parameter or changing type of a parameter are breaking changes.',
   nonBreaking: 'Non-breaking change is change that does not break backward compatibility with the previous version of API. For example, adding new operation or optional parameter is non-breaking change.',
-  risky: [
-    'A change requiring attention is a change that breaks backward compatibility according to the rules:',
-    'operation was annotated as deprecated in at least two previous consecutive releases and then it was deleted',
-    'operation is marked as no-BWC',
-  ],
+  risky: 'A change requiring attention is a change that potentially may break backward compatibility with the previous version of API, depending on the particular implementation of a client code. This category also includes breaking changes in operations annotated as no-BWC.',
   deprecated: 'Deprecating change is a change that annotates an operation, parameter or schema as deprecated. Removing a "deprecated" annotation is also considered a deprecating change.',
   annotation: 'An annotation change is a change to enrich the API documentation with information that does not affect the functionality of the API. For example, adding/changing/deleting descriptions or examples is annotation change.',
   unclassified: 'An unclassified change is a change that cannot be classified as any of the other types.',