add option in points_to_h3 to define field containing score

[danbjoseph]

now that we have more than one method for scoring (PIXELS and SEGMENTATION) the column with the score is not always gvi_score - allow the user to define what column to use.
@ioalexei maybe you want to take this on?

[ioalexei]

Sure thing - I'll look into it

[ioalexei]

started looking into this but the h3pandas package is throwing an error for me. I've logged an issue on the library - depending how long it takes to get a response, I might need to refactor slightly to remove the h3pandas dependency and reimplement using base h3. (If I need to do that I'll create a separate issue on here.)

[ioalexei]

DahnJ/H3-Pandas#33

h3 api has changed between v3 and v4, and h3pandas hasn't taken account of this yet.

• added h3 <4 as a dependency to pyproject.toml which fixes this until a proper fix is implemented in h3pandas

[ioalexei]

Summary of PR:

• Added argument to specify score field in points_to_h3
  • pixel_counting_gvi score was being read as string - unsure which step this is introduced in but I've added a check for the specified score field that tries to convert it to numeric and returns an error if it can't.
• Added argument to specify score field in create_webmap
• Updated Readme to reflect new command options for points_to_h3 and create_webmap
• Adds pinned dependency for h3 <4, which is a dependency of h3pandas (v4 of h3 instroduces breaking changes)