feat(geo-widget): backend storage implementation for geo widget

[dubsky]

This a first part of a two phase implementation of UI geo/map widget. This PR contains updates to swagger.yml (additions only, non breaking changes) to allow saving of the widget configuration. 'dashboard.go' serialization configuration has been updated accordingly.

• CHANGELOG.md updated with a link to the PR (not the Issue)
• Well-formatted commit messages
• Rebased/mergeable
• Tests pass
• http/swagger.yml updated (if modified Go structs or API)
• Feature flagged (if modified API)
• Documentation updated or issue created (provide link to issue/pr)
• Signed CLA (if not already signed)

[russorat]

@stuartcarnie could you take a look at the swagger changes?

[aanthony1243]

I added @GeorgeMac as a reviewer, please wait for his response before merging.

[glinton]

Don't forget to update pkger as well so this view type can be used in templates. iirc, common pkger files updated for a view type are clone_resource, parser, parser_models, and the parser/service_tests with an added testdata test. @TCL735 is a pro at these changes, you can look at his merged prs for an example.

[glinton]

feel free to add a similar prefix to the returned error, but remove this line

[glinton]

Thanks for making those additions, sorry for the delay on the re-review

[ivankudibal]

rebase of influxdata:master was done manually... A rebase with master of the fork, as suggested by github, is not preferred

[Palakp41]

❓ Is there a reason we are updating tests for xy in this pr? This seems a bit out of scope for geo.

[dubsky]

Yes, I did it because I have been adding extra test case specific to geo as requested. I wanted to make the source file to be more readable and make it obvious what are the individual cases testing. This individual addition means that you will get 'xy' or 'geo' serialization failed message if something goes wrong.

[danxmoran]

CI will probably fail until #20506 merges and this PR is updated to include it. It's under review now.