Fix RPB sort function for 'Not Applicable' cases

[HSenarath]

Follow up to #1592

To Do:

• [ ] Crown corps were given 'Not Applicable' value in RPB, but this is breaking the sort function because the columns now have both a string and number to sort. Fix the sort function to be able to handle 'Not Applicable' cases.
  • [ ] Decided to give crown corps null value instead so don’t need to modify sort function
• [x] Stop null values from being given a value of '0'
  • Currently RPB displays '0' when the csv has an empty value
  • in TableClass we gave any “.”, “”, “-” a value of zero so it doesn’t break other functionalities such as summing the column values of a csv
    • Changing this to give a value of null instead (This doesn’t cause any issues with the summing function, but need to check if it’ll break anything else on the site)
• [ ] When populating programSpending remove any pipeline generated planned spending calculations
  • it’s using the old Table API instead of graphQL?
• [ ] On ‘Authorities and Expenditures’ panel ensure consistency between the items selected in the legend and the ‘Table of Data’ view
• [ ] Write unit tests

In the future, instead of retroactively removing the pipeline generated planned spending values for crown corps maybe the pipeline shouldn’t generate these values in the first place.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 12 lines in your changes missing coverage. Please review.

Project coverage is 7.06%. Comparing base (0243395) to head (e39f78c). Report is 2 commits behind head on master.

Files with missing lines	Patch %	Lines
...lient/src/components/DisplayTable/DisplayTable.tsx	0.00%	11 Missing :warning:
client/src/rpb/granular_view.js	0.00%	1 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #1621 +/- ## ========================================= - Coverage 7.07% 7.06% -0.01% ========================================= Files 395 395 Lines 14435 14442 +7 Branches 3584 3589 +5 ========================================= Hits 1021 1021 - Misses 13414 13421 +7 ``` | [Flag](https://app.codecov.io/gh/TBS-EACPD/infobase/pull/1621/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=TBS-EACPD) | Coverage Δ | | |---|---|---| | [client](https://app.codecov.io/gh/TBS-EACPD/infobase/pull/1621/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=TBS-EACPD) | `3.10% <0.00%> (-0.01%)` | :arrow_down: | | [form_backend](https://app.codecov.io/gh/TBS-EACPD/infobase/pull/1621/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=TBS-EACPD) | `87.85% <ø> (ø)` | | | [server](https://app.codecov.io/gh/TBS-EACPD/infobase/pull/1621/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=TBS-EACPD) | `33.91% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=TBS-EACPD#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[HSenarath]

Was trying to do too much in one PR, so simplified the tasks to:

• [x] Give planned spending type: "dollar", currently it's set as "big_int so it's missing the '$' in the table which is inconsistent with the rest of the spending rows
• [x] Crown corp planned spending given - value instead of 'Not Applicable'
• [x] Set text-align to center for any '-' values in the rpb
• [x] Separate ticket in titan repo to address the negative planned spending values found