Feature/atr 557 dev check exceptions for serialization

[SENya1990]

Merge after ATR-139!!!

High level overview.
@EAndrosova this may be useful for the documentation of new diagnostics.

Diagnostics:

• Implemented diagnostic PX1063 to check that exception-derived classes always declare serialization constructor.
• Implemented diagnostic PX1064 to check that exception-derived classes declaring new serializable data always provide an override for the GetObjectData method.

By serializable data analysis understands any new data declared in the exception class that will be serialized by .Net serializers and Acumatica reflection based serializer:

• New instance fields if they are not marked with System.NonSerializedAttribute attribute:

public int Field = 3;

• New instance auto generated properties if they are not marked with System.NonSerializedAttribute attribute:

public int Property { get; set; } 

Some examples of what won't be considered serializable:

• static fields and constants
• static properties
• calculated properties:

public int Property => 4;

• properties with explicit backing field:

public int Property 
{
   get =>  _fieldFromBaseClass;
   set 
   {
       _fieldFromBaseClass = value;
   }
}

• fields and properties marked as non serializable:

[field: NonSerialized]
public int Property { get; set; } 

Code Fixes:

• Implemented code fix for PX1063 that will generate the missing serialization constructor for the exception class.
  The generated constructor will be private for sealed exception classes and protected for all other classes.
  The generated constructor will call the base serialization constructor.

If exception declares a new serializable data then the constructor will contain a call to the RestoreObjectProps static method of the PX.Common.ReflectionSerializer class. This class is responsible for Acumatica custom reflection-based serialization and deserialization of data. If there is no serializable data then the serialization constructor body will be empty.

• Implemented code fix for PX1064 that will generate the missing GetObjectData override that will contain two statements:
  - First, a call to the GetObjectData static method of the PX.Common.ReflectionSerializer class
  - Second, a call to the base GetObjectData method:
  csharp base.GetObjectData(info, context);

• In case of an old version of Acumatica there is no PX.Common.ReflectionSerializer class because it was added as a refactoring later. PX.Common.PXReflectionSerializer class will be used instead, the names of the methods are the same,

• Code fixes will add all required missing using directives

Other Changes:

• Added code generation utils to add missing using directives
• Refactored DAC PK/FK related code fixes
• Fixed a bug in the analysis of long operation started in graph view delegates when graph extension is passed to the StartOperation method (@EAndrosova , this is useful for release notes)
• Added examples for new diagnostics to the demo solution
• Added unit tests for diagnostics and code fixes
• Updated Acumatica dlls used by demo solution and unit tests to 2022r200
• Reworked unit tests infrastructure:
  - Added new metadata reference to netstandard.dll to the project dynamic generation
  - Added syntax parsing and compilation options
  - Added option to not use concurrent analysis when unit tests are debugged

[dropsonic]

@SENya1990 high-level overview is declared but missing

What is the point of removing dots from the end of each diagnostic's title?

[SENya1990]

@EAndrosova please review diagnostic and code fix messages for PX1063 and PX1064

[EAndrosova]

Please change to the following (too many nouns in a row + Acumatica is the company name so we should specify ERP)
The declaration of the exception class does not contain a serialization constructor. This will cause an incorrect deserialization of the exception data and will lead to runtime errors in Acumatica ERP.
The declaration of the exception class introduces new serializable fields but does not declare an override for the GetObjectData method. This will cause an incorrect deserialization of the exception data and will lead to runtime errors in Acumatica ERP.

[SENya1990]

done

[SENya1990]

@dropsonic , high level overview was missing because I was writing it. I added an important warning first and then started writing it.

The dots were removed because:

• The style of the messages was not consistent. Most of the diagnostic and code fixes messages didn't have dots but some of them did.
• Microsoft own diagnostic messages do not use dots:
  

[SENya1990]

@EAndrosova please review the changes in the read.me file

[EAndrosova]

Please change to the following:
You can use older versions of Acumatica ERP DLLs but there is no guarantee that Acuminator will work correctly. The current recommended version is Acumatica ERP 2022 R2 without minor updates.

If possible, specify RC or GA to make more clear what "no minor updates" mean.

[SENya1990]

done

[EAndrosova]

Please change to the following (too many nouns in a row + Acumatica is the company name so we should specify ERP)
The declaration of the exception class does not contain a serialization constructor. This will cause an incorrect deserialization of the exception data and will lead to runtime errors in Acumatica ERP.
The declaration of the exception class introduces new serializable fields but does not declare an override for the GetObjectData method. This will cause an incorrect deserialization of the exception data and will lead to runtime errors in Acumatica ERP.

[EAndrosova]

Please change to the following:
You can use older versions of Acumatica ERP DLLs but there is no guarantee that Acuminator will work correctly. The current recommended version is Acumatica ERP 2022 R2 without minor updates.

If possible, specify RC or GA to make more clear what "no minor updates" mean.

[SENya1990]

@EAndrosova please verify the code fix messages.

[SENya1990]

@dropsonic turns out MS style for diagnostic messages has different rules for dots in messages that consist of one sentences and messages composed from multiple sentences:

• No dots for single sentences
• Dots at the end of all sentences if there are two or more sentences

After discussion with @EAndrosova it was decided to be consistent with MS style, so I returned dots for all Acuminator messages consisting of several sentences and added a paragraph about these rules to the coding guidelines.