feature: Issue #17 - Registration Number Policies

[PooriaT]

Description

Issue Link: Mock policies for registration number #17

In this issue, a verification for the registration number is provided. First, the registration number has to be validated. Then, it should be checked whether it is available in Vancouver Open Data.

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.

[nam-m]

I think the policy structure is good, and it's very readable.
You don't need to call the API in here though, because it is handled in #38

[nam-m]

Thanks for your update

2 changes I recommend are:

1. Remove total_count check in the policies
2. In the tests, you can set registration numbers one time outside(maybe parametrize too), and let all tests go through these