samples: update TODO section

[averikitsch]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

[averikitsch]

.origin will strip the GCF url of the actual function route. I have tested with Cloud Run and it works either way.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[averikitsch]

@googleapis/yoshi-nodejs PTAL

[JustinBeckwith]

One issue with the snippet we should discuss - also, please use docs: or samples: - when you use fix:, it signals to the release tooling that this should cause a release. This PR doesn't have any material impact on the library code, so we wouldn't want to do that.

[JustinBeckwith]

As written, this code would fail because we're using a const instead of let, and trying to assign down on line 40. Would another option here be moving const {URL} = require('url'); with the other requires, and always doing the assignment of const targetAudience = new URL(url) on line 32?