Accept display options for MathesarMoney type

[silentninja]

Fixes #1105 by adding display options support for MathesarMoney type.

Features List

• The frontend should be able to set any of these display options.

• mathesar.tests.api.test_column_api.test_column_create_display_options

• The frontend should know what the choices are for any display option that supports a set of choices.

• mathesar.tests.api.test_ui_types_api.test_type_list

• mathesar.api.display_options.money_display_options_schema

• The display options should be validated.

• mathesar.tests.api.test_column_api.test_column_create_wrong_display_options

• If any of the display options end up changing other display options, the backend should handle that.

  • mathesar.tests.api.test_column_api.test_column_update_mathesar_money_display_options

• When we infer a column as a money type, we should set the display options for that column based on the currency symbols in the original CSV/other file.

• mathesar.tests.display_options_inference.test_money.test_display_options_inference

Additional fix

• Fix DRF error mixin to allow custom error exceptions inside Serializer validations

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the master branch of the repository
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no
  visible errors.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[silentninja]

Blocked by #1335

[seancolsen]

I haven't looked at the diff at all here. (It's kind of baffling to me that so many changes would be required for what seems like a relatively limited addition to the API, so I haven't even bothered to try understanding what's going on under the hood.)

I did verify that the API is working as I need it to work though.

The following display options, seem to work well according to these recent and somewhat ad-hoc specs:

• number_format
• currency_symbol
• currency_symbol_location

And that's all I need in order to continue working on #259, so I'd like to get this merged.

But I'll hold off on merging until we get a proper backend review.

[kgodey]

@seancolsen Most of the complexity here is because money has required display options that we need to set from the backend. If we infer a column in a CSV as MONEY, we need to also figure out what the currency is and set the display option accordingly. No other type has anything like that.

I've assigned @mathemancer to review this since it touches type casting logic.

[mathemancer]

I think this looks good. Let's get it merged!

[mathemancer]

Ach, it has merge conflicts. @silentninja Go ahead and merge after resolving those.