Bump go.mod version to v2

[pbusko]

Summary

To reflect the actual major version and follow the official recommendation regarding go.mod versioning

Use Cases

https://go.dev/doc/modules/version-numbers

A major version update to a number higher than v1 will also have a new module path. That’s because the module path will have the major version number appended, as in the following example:

module example.com/mymodule/v2 v2.0.0

A major version update makes this a new module with a separate history from the module’s previous version. If you’re developing modules to publish for others, see “Publishing breaking API changes” in Module release and versioning workflow.

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
• I have added an integration test, if necessary.
• I have reviewed the styleguide for guidance on my code quality.
• I'm happy with the commit history on this PR (I have rebased/squashed as needed).

[pacostas]

Hello @pbusko 👋 ! Thank you for your contribution :) Can you describe how consuming the versioned node-start from the node-start module will benefit the node-start module? I'm asking for a little bit of context as this change makes sense for consuming external modules, but I can not find a scenario where the same module would benefit from not consuming the latest version of itself. Also, it seems that this change is adding an extra step during development, as for consuming the latest version of the node-start you will have to make a publish first.

[pbusko]

paketo-buildpacks/node-engine#966 (comment)

[pacostas]

LGTM

I need to clarify the actual benefits of this PR and in case we need to follow a versioning we need to consider strategy for that.

[c0d1ngm0nk3y]

see discussions on paketo-buildpacks/node-engine#966

[pacostas]

Related issue paketo-buildpacks/nodejs#913

[mhdawson]

Based on discussion in paketo-buildpacks/nodejs#913 we'll land these add hock for now. @pbusko can you rebase and then I'll land.

[mhdawson]

LGTM but a rebase will be needed.

[pbusko]

Thank you @mhdawson, the PR has been rebased

[pacostas]

Based on this paketo-buildpacks/nodejs#913 (comment) , LGTM

[mhdawson]

@pbusko unfortunately seems to need another rebase. Will enable auto-merge so it should land as soon as the tests pass. I had started them yesterday but seems there was some change between then and now.

[pacostas]

@pbusko can you rebase again?

[pacostas]

@pbusko can you rebase once more? I thought the auto merge was enabled and in the mid-time another PR automatically landed. sorry :)

[pbusko]

@pacostas could you please re-trigger the integration tests? Yet another failure due to the network issues while downloading nodejs package.