Consider using the CLI config format for the VS extension

[ErikEJ]

Now that most features are supported by the CLI, we could consider using the CLI config format instead of the efpt.config.json format.

WHY?

• the new format is much more readable, and recently "tooltip" support was added for it in VS.
• this will also light up the object filtering available in the CLI config file.

Missing features

                // Not supported:
                UseHandleBars = false,
                SelectedHandlebarsLanguage = 0, // handlebars support, will not support it
                OptionsPath = null, // handlebars support, will not support it (looks like it is not used!)

                // Not implemented:
                UseNoDefaultConstructor = false, // not implemented, will consider if asked for
                DefaultDacpacSchema = null, // not implemented, will consider if asked for
                UseNoObjectFilter = false, // will always add all objects and use exclusions to filter list (for now)
                UseAsyncCalls = true, // not implemented
                FilterSchemas = false, // not implemented
                Schemas = null, // not implemented

Design thoughts:

We already have a method (mapper) to convert a CLI config file to ReverseEngineeerOptions used by the VS extension.

If there is only a single efpt.config.json file in the project, we could silently just save using the CLI format, and get rid of the old file (rename to .bak)

If there are more eftp.config.json files, leave everything as is.

Add global option to opt out of this, to stay on the old format (for now)

We could also decide to not convert if any of the not supported/not implemented features are in use.

@jwyza-pi FYI!