Inconsistent naming standards on casing in schemas

[bingenito]

Minor Issue

Inconsistent naming standards on casing in schemas

Area of Issue

• App Directory
• API
• Context Data
• Intents
• Desktop Agent Bridging
• Use Cases
• Other

Issue Description:

Through time, with no enforced naming standards on casing, there is inconsistency across context schemas. The issue becomes more apparent when porting to other language platforms. For example, in .NET when configuring JSON serializers, a custom serializer is required for any types that do not match the configured majority default. While I feel we are passed the point of being able to change for consistency, we can at least pick a convention and enforce for future additions through linting.

Scope:

• Decide on new default casing strategy
• Configure linting to fail on mismatch

Additional Context:

Compare newer TransactionResult using pascal case values vs something such as ChartStyle.