Support @constraint annotation mapping for Ballerina to OpenAPI

[lnash94]

• Primitive type: Integer : (ballerina mapping) int
  

format	keywords	Ballerina Mapping
int32		int
int64		int
	minimum	@constraint:Int {   minValue: <value>}
	maximum	@constraint:Int {   maxValue: <value>}
	exclusiveMinimum	@constraint:Int {   minValueExclusive: <value>}
	exclusiveMaximum	@constraint:Int {   maxValueExclusive: <value>}
	multipleOf

• Primitive type: float (ballerina mapping) : float
  

format	keywords	Ballerina Mapping
	minimum	@constraint:Float {   minValue: <value>}
	maximum	@constraint:Float {   maxValue: <value>}
	exclusiveMinimum	@constraint:Float {   minValueExclusive: <value>}
	exclusiveMaximum	@constraint:Float {   maxValueExclusive: <value>}
	multipleOf

• Primitive type: Double (ballerina mapping) : decimal
  

format	keywords	Ballerina Mapping
	minimum	@constraint:Number {   minValue: <value>}
	maximum	@constraint:Number {   maxValue: <value>}
	exclusiveMinimum	@constraint:Number {   minValueExclusive: <value>}
	exclusiveMaximum	@constraint:Number {   maxValueExclusive: <value>}
	multipleOf

• Primitive type: String (ballerina mapping) : string
  

format	keywords	Ballerina Mapping
	minLength	@constraint:String {   minLength: <value>}
	maxLength	@constraint:Stringl {   maxLength: <value>}
(not support from OpenAPI)	length	@constraint:Stringl {   length: <value>}
	pattern

• Array type: String (ballerina mapping) : array
  

format	keywords	Ballerina Mapping
	minItems	@constraint:Array {   minLength: <value>}
	maxItems	@constraint:Array {   maxLength: <value>}
	uniqueItems

• Object type: object schema (ballerina mapping) : record type
  

format	keywords	Ballerina Mapping
	minProperties
	maxProperties

• Apply this for object schema to record type mapping
• Apply for type definitions

[lnash94]

When implementing a fix for this issue we encountered a blocker with accessing the value in annotation fields whose types are in separate modules and third-party package. (ex: central pushed).

There are three solutions have been suggested :

1. Change constraint annotations implementations into const and try to use semantic APIs attachment point API
2. Improve the Semantic API for accessing the non-const annotation field value.
3. Change the OpenAPI tool input into taking the ProjectAPI and process.

Describe your problem(s)
Among the 3 solutions passing projectAPI into the tool still has problems with

1. accessing the annotation value which are in separate packages.
2. It causes some API changes to the whole Ballerina to OpenAPI tool. Although we passed it there still we have done some kind of process finding dependency graphs for tracking dependencies to access the type defined in the separate package. It will cause some kind of conflict to the current util since it may additional processes to mapping. Complexity can be delayed to generate openAPI spec, resolving dependency issues, intermittent issues etc. (This util has been used in several modules http, choreo, vsCode. Therefore we required to safe method to solve this.)

[lnash94]

Close with the favour with this issue #4788