[KED-1076] Add open flag to build-docs that opens the documentation on build

[mzjp2]

Notice

• I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

• I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

• I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

• I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

Motivation and Context

Why was this PR created?
Closes #86

How has this been tested?

What testing strategies have you used?
Similar testing strategy as kedro.cli with docs.

Checklist

• Read the contributing guidelines
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added new entries to the RELEASE.md file
• Added tests to cover my changes
• Assigned myself to the PR

[mzjp2]

Turns out the issue was using pathlib's resolve, in Python3.5 if the filepath doesn't exist (as it doesn't when being mocked), an error is thrown, necessitating the use of mocking that method on the Path object.

Incidentally, whilst researching this issue, I came across a few articles about the smell and danger of using .assert_called_once which the existing Kedro test that mocks webbrowser uses (and nowhere else) here:

https://github.com/quantumblacklabs/kedro/blob/d2c9648794cdda5ad28ea99cfc2661c076876932/tests/cli/test_cli.py#L185-L188

I think this would be better if patched_browserr.assert_called_once() was replaced with patched_browser.call_count == 1 (I didn't think raising an issue or a PR was necessary for such a a tiny thing).

[mzjp2]

Not sure it's worth editing the documentation (https://github.com/quantumblacklabs/kedro/blob/develop/docs/source/03_tutorial/05_package_a_project.md or https://github.com/quantumblacklabs/kedro/blob/develop/docs/source/06_resources/01_faq.md) so I haven't, but if you think it should - I'm happy to.

[lorenabalan]

Awesome, thanks for picking this up! 🎉 I've left a couple of comments, happy to approve once they are addressed! :)

[lorenabalan]

Not sure it's worth editing the documentation (https://github.com/quantumblacklabs/kedro/blob/develop/docs/source/03_tutorial/05_package_a_project.md or https://github.com/quantumblacklabs/kedro/blob/develop/docs/source/06_resources/01_faq.md) so I haven't, but if you think it should - I'm happy to.

Just saw this, sorry. Maybe a note in 05_package_a_project.md would be nice ("to quickly inspect this, run my awesome command"), but I wouldn't worry about it, it's far from being a blocker on merging this.

[lorenabalan]

Maybe a note in 05_package_a_project.md would be nice

Actually template/{{cookieutter.repo_name}}/README.md would be more relevant.

[lorenabalan]

LGTM! 🚀

[DmitriiDeriabinQB]

Nice! 👏