Feature/create api client policy module

[nam-m]

Description

Issue Link: #19

This PR contains client class implementation for Business Licences in Vancouver Open Data Portal.

Since we only use Business Licences for now, the BASE_URL is set to "https://opendata.vancouver.ca/api/explore/v2.1/catalog/datasets/business-licences/records", and the supporting class methods will help add parameters to this URL

The query works by using "where" clause to filter the dataset, and "select" clause to choose return parameter.
For instance, setting where: businesstype="Short-Term Rental will filter the dataset for short-term rental businesses only.
And setting select: status will return the licence number status only.

Licence number validity check (string format, length,...) is omitted as this should be implemented in the Policies, so it is assumed that the status query will always return meaningful results

Type of Change

Please delete options that are not relevant.

• 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?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

• Unit Test
• Integration Test
• E2E Test

Checklist:

Before you submit your pull request, please make sure you have completed the following:

• I have read the CONTRIBUTING document.
• I have checked that my code adheres to the code style of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• 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.
• Any dependent changes have been merged and published in downstream modules.

Screenshots (if applicable)

Since we don't have pytest in CI yet, here's the test result

Additional Notes

Note that "licence" is used instead of "license" (grammar)

• Interesting find:
  • For "Inactive" status, there's often another one with a different status. Hence, one licence number will return 2 statuses, in which one is "Inactive".
  • I found that some listings used inactive licence from another business

[umsu2]

Policies should have the same interface. this is 3 polices combined together.

class PolicyA:

def is_valid(): bool
def description(): ...

class PolicyB:
def is_valid(): bool
def description(): ...