Add Money cell and Money type options UI

[seancolsen]

Fixes: #259

Before

• No way to make a Money column

After

• You can change the column type to "Money".
• You can configure the type options for it.
• The cell shows the currency symbol during display (but not edit).

Notes

• Many of the requirements have changed since the ticket was written, and it's difficult to summarize all of them here. @pavish I'm hoping that you'll have enough of an idea of the requirements to review this PR, and we can address subsequent issues as we discover them.

• This PR only handles the case where the user is creating a new column with the MATHESAR_TYPES schema installed. We use the type MATHESAR_TYPES.MATHESAR_MONEY. I haven't yet tested this functionality with the built in Postgres MONEY type, but I suspect more work will be needed to handle existing data of that type. I created Allow the user to work with Postgres MONEY values with our Money UI type #1403 for that work.

• While setting the default Money column value and while setting a filter condition for a Money column, the input does not display the currency symbol. This behavior is not ideal, but it still works, in my opinion. I'm not sure of the best design to employ to improve this situation. If we want to improve it, we'll need to give the UX some more thought.

• The ticket says "shown in a monospace font". That's not implemented here. I'd argue it's not necessary. We can create another ticket for it if needed.

• There's quite a bit of code duplication between Number functionality and Money functionality. I'm open to cleaning some of it up, but I'd like the dust to settle a bit first.

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.

[pavish]

@seancolsen @silentninja I am not able to save a Money type column here.

1. When trying to convert a column to money type with empty values for decimal places and max digits, server throws error: the fields cannot be null.
2. When values are entered for both, server throws error: Unknown type_option passed.

[seancolsen]

@pavish Yeah that's an issue that I brought up with @silentninja back when I was first working on this PR a couple months ago. My memory is hazy, but I vaguely recall there being an open ticket or open PR for that somewhere. I just went looking and couldn't find it though. @silentninja does this jog your memory? Do you know of a ticket or PR for this bug? If we don't have a ticket for that yet, then I'm happy to create one. But I don't think it needs to hold up this PR. @pavish you can continue your review by manually submitting the columns PATCH request without the type_options parameter. Then you can convert the column to Money and play with its behavior. You can even change its display options as long as you make sure to remove the type_options parameter from other PATCH requests to the columns endpoint too.

[silentninja]

@pavish @seancolsen I think the issue is #1359

[seancolsen]

Thanks @silentninja I'll make fixes in this PR. @pavish I'll ping you when it's ready for review.

[seancolsen]

@pavish this is ready for re-review now.

• In 0cc393c I removed the DbTypeSelect component as you recommended via chat. I also removed DbOptionsForm, placing its contents inline within AbstractTypeOptions because it was much simpler without DbTypeSelect.
• In ae9fcb4 I removed the SCALE and PRECISION DB type options.

[pavish]

@seancolsen Looks good to me.