ft: add typescript

[shyakadavis]

What does this PR do?

• Fixes Add TypeScript Type Definitions  #26 by re-writing everything in TypeScript
• Modifies the methods for accessing the data.

e.g.

Before, to access districts, it was:

const { Districts } = require('rwanda');

console.log(Districts('kigali')); // [ 'Gasabo', 'Kicukiro', 'Nyarugenge' ]
console.log(Districts('Kigali', 'South')); // [ 'Gasabo', 'Kicukiro', 'Nyarugenge', 'Huye',.... ]

But now, to ensure consistency and type-safety at least, you pass a single object param, whose properties are required, in order to maintain/retain familiarity with the package.

import { Districts } from "rwanda";

const districts = Districts({ provinces: "Kigali" }); // [ 'Gasabo', 'Kicukiro', 'Nyarugenge' ]
const districts = Districts({ provinces: ["Kigali", "North"] }); // [ 'Gasabo', 'Kicukiro', 'Nyarugenge', 'Huye',.... ]

Description of Task to be completed?

• This will:
  • set up a pnpm workspace monorepo with:
    • an apps dir for the docs site, and
    • a packages dir which will host the actual rwanda package.
• Versioning will be automated with the help of the changesets package
• Testing will be made easier with Vitest
• This will also drastically simply linting and formatting with the near-zero config toolchain, biome
• Introduce pre-commit hooks for formatting and testing with husky
• Re-write all internal methods.
  • Provinces
  • Districts
  • Sectors
  • Cells
  • Villages
• Re-write all data in TS
  • East
  • Kigali
  • North
  • West
  • South
• Write all tests

How should this be manually tested?

• pnpm test in the root dir.
• If you wish to test the package in a real app locally, navigate into the apps/www dir, hit pnpm i, and hit pnpm dev. You'll notice a bunch of type errors in the src/routes/+page.svelte, which are a demonstration of type violations. Correct them, and in localhost:5173, you should see the correctly rendered data.

Any background context you want to provide?

• PNPM and Vite seemed the logical backbones for this. They have excellent D/X, imo.
• Would have liked to make all param properties optional, i.e., one could just access the villages of a district or villages of a province, without having to pass all other params, only what you need, but I guess that would be considered in another release.
• Since this P.R has gotten too broad, I plan to open another for the docs creation. That is, if the current one is accepted.
• I didn't know the effect typing vars that hold tens-of-thousands of values would have on performance and/or bundle size, so I just left typing for provinces, districts, and sectors

Screenshots (if appropriate)

• N/A