LF-4625a Update controller for sensor addition

[kathyavini]

Description

This is the first part of the updated controller(s) for sensor addition, and contains:

• a new route + controller to connect farms with Ensemble organizations based on what we learned today
• refactors on the old sensor addition controller as specified in the original Jira ticket (readability refactor + removing CSV parsing)

I wrote the refactors before we did the about turn in terms of backend architecture. I thought we might as well use them to make it that much clearer what the original flow did, before we start adjusting it. But it's a bit optional as the code I refactored will be eventually dropped anyway.

Jira link: https://lite-farm.atlassian.net/browse/LF-4625

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Passes test case
• UI components visually reviewed on desktop view
• UI components visually reviewed on mobile view
• Other (please explain)

Link or update organization with a simple POST to /sensor/associate_esci_org/

Request should be (you can use any org UUID registered to our Ensemble user, and the one below does work)

{
    "organization_uuid": "9f48cb5d-9f96-4e16-92f7-c680f27f09da"
}

I'm not sure the exact use case at this point (probably none), but with the refactor it is also now possible to add sensors via Postman instead of CSV; the request body just needs to follow the CSV format:

E.g. this will add a sensor within the bounds of UBC Farm

[
    {
        "latitude": 49.250400,
        "longitude": -123.238075,
        "name": "UBC Farm Sensor 1",
        "reading_types": [
            "temperature",
            "soil_water_potential"
        ],
        "external_id": "27383A",
        "depth": 0.1,
        "brand": "Non-Ensemble"
    }
]

Checklist:

• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The precommit and linting ran successfully
• I have added or updated language tags for text that's part of the UI
• I have added "MISSING" for all new language tags to languages I don't speak
• I have added the GNU General Public License to all new files

[kathyavini]

This is where I would very much like to see a secondary check, maybe on email or farm name? But we would have to coordinate with Ensemble to make sure their organization registration included it.

[Duncan-Brain]

For some reason I am hesitant to just partially remove the CSV option haha. It mostly works but just doesn't meet ideal design and needs to be adapted for new fields maybe. I can't deny I am partial to leaving it in place for custom sensors 🥲

And maybe editing sensor controller right now won't be necessary if you agree that it is rest-ful to work on the /farm_external_integration resource instead.

[kathyavini]

I'll defer to @antsgar on the CSV upload; there will be no way to access it anymore from app is why I think it's okay to remove now, but you're right it's a partial removal as I only adjusted in this particular controller. That was just my understanding of the ticket requirements, but really there is a lot more code that can be deleted (from shared and webapp) if we are wiping CSV upload entirely. That deletion might be best in its own PR so even if we rebuild CSV addition from the ground up when we re-introduce it (which is what I believe we're going to do), we'll have just one place to look for all of the original code.