Restructured these modules for ease of mainteance and apply the single
responsibilty principle (wherever is applicable).

* SchemaView

 - Split the code based on the functionality, and responsibility.
 - Introduced a new View 'InlineView' instead of using the
   'nextInline' configuration of the fields to have a better, and
   manageable view.
 - Using the separate class 'SchemaState' for managing the data and
   states of the SchemaView (separated from the 'useSchemaState'
   custom hook).
 - Introduced three new custom hooks 'useFieldValue',
   'useFieldOptions', 'useFieldError' for the individual control to
   use for each Schema Field.
 - Don't pass value as the parameter props, and let the
   'useFieldValue' and other custom hooks to decide, wheather to
   rerender the control itself or the whole dialog/view. (single
   responsibilty principle)
 - Introduced a new data store with subscription facility.
 - Moving the field metadata (option) evaluation to separate place
   for better management, and each option can be defined for a
   particular kind of field (for example - colleciton, row, cell,
   general, etc).
 - Allow to provide custom control for all kind of Schema field.

* DataGridView

 - Same as SchemaView, split the DataGridView call in smaller and
   manageable chunks. (For example - grid, row, mappedCell, etc).
 - Use context based approach for providing the row and table data
   instead of passing them as parameter to each and every component
   separately.
 - Have a facility to extend this feature separately in future.
   (for example - selecatable cell, column grouping, etc.)
 - Separated the features like deletable, editable, reorder,
   expandable etc. cells using the above feature support.
 - Added ability to provide the CustomHeader, and CustomRow through the
   Schema field, which will extend the ability to customisation better.
 - Removed the 'DataGridViewWithHeaderForm' as it has been achieved
   through providing 'CustomHeader', and also introduced
   'DataGridFormHeader' (a custom header) to achieve the same feature
   as 'DataGridViewWithHeaderForm'.

Also - Modified the testcases to use separate 'Schema' objects for
testing the rendering of create, edit, and properties mode as
BaseUISchema instance share the same SchemaState object.

…de will mangled the name of the component function, which would lead to 'View not found' error.

reset the tab only, when reset key is changed.

the data.

I never realised that - we were using 'origData' for schema
validation to get the initial data, and replaced it with 'sessData'
variable by mistake. Changing it back to use 'origData' based on the
feedback from Aditya.

jumping issue. It fixes pgadmin-org#7878.

Reference:
- https://dev.to/kwirke/solving-caret-jumping-in-react-inputs-36ic

TODO:: Yet to work on the issues for the partition and table dialog UI.

…s fix.

option for the field having no 'id'. e.g. a field with type
'nested-tab', 'nested-fieldset'.

…bject change.

row details. It fixes the dashboard issue, where activity table was
showing same query for all the rows. [pgadmin-org#7895]

…on from the left side object explorer. pgadmin-org#6502