Add pricing model parameter validation table

(One paragraph: the idea.)

(Motivation, problem being solved, related context.)

PricingModelConfig models the pricingengine.xml file. Currently the parameters field is an unvalidated key-value blob:

• There is no record of which parameters are valid for a given model type.
• Parameter types are not enforced at insertion.
• The UI does not guide the user to the correct fields for a chosen model.

Proposed changes:

• Add a ores_analytics_pricing_model_parameters_tbl table: (model_type_code, parameter_name, parameter_type, is_required, description).
• Seed it with known ORE pricing model parameters on database setup.
• Validate inserted configs against the table via a DB trigger or service-layer check.
• In the pricing model config form, when the user picks a model type, dynamically render only the relevant parameter fields with the correct input widget (text, number, date).