Frontend: use API to show list of polling stations on polling station select page

[cikzh]

This PR replaces hard coded polling stations with polling stations provided by the backend. It also adds a lookup when the user enters a polling station number.

[cikzh]

When I hover over "Bekijk de lijst met alle stembureaus", I have an I-cursor (the text selecting one) instead of a pointer cursor.

That's weird, that was fixed here: #143. I'll rebase main

[praseodym]

Two things I noticed in my brief look at the preview environment:

• The search design doesn't match the design in Figma.
• If I enter a number that is not found, I can still continue to the data entry page.

[cikzh]

@praseodym

* The search design doesn't match the [design in Figma](https://www.figma.com/design/zZlFr8tYiRyp4I26sh6eqp/Kiesraad---Abacus-optelsoftware?node-id=137-5073&t=HbflVzrg2pppVyBy-4).

Added the styling

* If I enter a number that is not found, I can still continue to the data entry page.

This will be fixed in #108

[cikzh]

• the 'eerste/tweede invoer' badge after the name of the polling station is missing

@jorisleker I've fixed the design issues and added a debounce on the user input. I purposely left the badge out, as @jschuurk-kr mentioned earlier in a review that we should leave out design placeholders, and the badge logic is not implemented yet.

[jschuurk-kr]

• the 'eerste/tweede invoer' badge after the name of the polling station is missing

@jorisleker I've fixed the design issues and added a debounce on the user input. I purposely left the badge out, as @jschuurk-kr mentioned earlier in a review that we should leave out design placeholders, and the badge logic is not implemented yet.

My reasoning about the placeholders: I was starting to find it hard to look at the page, check what's in scope of the PR, identify which parts of the page had been implemented and which parts are placeholders, and then decide what to review/test for the PR. That left me with less mental bandwidth for testing/reviewing than I liked.

So for pages we're actively working on, I'm in favor of either removing placeholders or having placeholders that are clearly placeholders. In this case that could be the badge saying "invoerstatus" instead of "1ste invoer".

[praseodym]

The PR description still says:

The PR is still in draft, because it lacks some test coverage, but it is otherwise ready for review.

I think that's outdated and can be removed?

[cikzh]

• the 'eerste/tweede invoer' badge after the name of the polling station is missing

@jorisleker I've fixed the design issues and added a debounce on the user input. I purposely left the badge out, as @jschuurk-kr mentioned earlier in a review that we should leave out design placeholders, and the badge logic is not implemented yet.

My reasoning about the placeholders: I was starting to find it hard to look at the page, check what's in scope of the PR, identify which parts of the page had been implemented and which parts are placeholders, and then decide what to review/test for the PR. That left me with less mental bandwidth for testing/reviewing than I liked.

So for pages we're actively working on, I'm in favor of either removing placeholders or having placeholders that are clearly placeholders. In this case that could be the badge saying "invoerstatus" instead of "1ste invoer".

In this case the Badge is typed in an object, so I'd have to add a placeholder field, or create a seperate placeholder badge, so I'll just leave it out for now. The Badges are still present in the code as commented TODO's, so they'll be trivial to find and implement, once we get to that.

[praseodym]

Even though the UI says "SHIFT + Enter", a regular Enter keypress also submits (navigates to the data entry form). The data entry form also doesn't handle this, maybe @lkleuver has already resolved it there as part of #133?

[cikzh]

Even though the UI says "SHIFT + Enter", a regular Enter keypress also submits (navigates to the data entry form). The data entry form also doesn't handle this, maybe @lkleuver has already resolved it there as part of #133?

This is now fixed

Fixed

[cikzh]

I think all feedback is either implemented or delegated to other issues