Filtering by N/A BORO ID doesn't work [4]

[BCerki]

Describe the Bug:

If you type n/a into the grid search box, you don't get the N/A records. This is because the filtering searches the boro id in the db, and we don't have "N/A" in the db. "N/A" is added on the front end.

We have the same situation in the transfer grid and using filtering_including_not_applicable in the service should fix it.

Probability: 3

(How likely the bug is to happen, scored from 1-5. For example, probability of 5 is something like "it happens to all users every time they log in." whereas probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")

Impact: 1

(How bad the bug is when it does happen, scored from 1-5. For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected." whereas effect of 1 is "It makes some styling look a little bit weird.")

Steps to reproduce the behaviour:

1. Step Lets use common phrasing #1
2. Step Add missing topics #2
3. Step Add project lifecycle badge #3

Screenshots:

Additional information:

OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]

Additional Context