Keep comments in .cats.txt - compatibility for addon devs

Current behavior:

When adjusting asset categories the .cats.txt (CDF) file is re-generated and any altercations, such as user notes or stored data, are removed

Proposed behavior:

Retaining comments or specific marked lines between generated versions of the .cats.txt files

Reasoning:

With addon dev and the asset browser it is currently hard to transfer relevant information generated from an addon between computers working in the same library without resorting to another file within the same directory as the .cats.txt file.

This results in a more difficult time for addon developers to expand on the information utilized in the asset browser and addons related to it. In the case of a post processing script to retrieve and re-add the comments on save, any user that doest have such an addon installed removes the information from the system

Proposed possibilities from simple to complex:

• Retain comment header block
• Retain data marked with a symbol
• Prev and expose to python api via prop group

Use cases:

• Addon for standard tags throughout a library
• Addon for retrieving info on files from stream in pf helix or similar
• Addon for adjustments to behavior related to categories

TLDR:

Keeping comments or additional info between .cats.txt file iterations would allow addon developers to store information relevant to any number of users of that asset library, allow for the expansion of addons relevant to the internal asset browser.