docs: add upcoming angular conferences

[mgechev]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

[petebacondarwin]

Apparently there will be ngPoland at the same time as EnterpriseNG.

[sonukapoor]

@mgechev CI currently fails to detect PRs if they come from angular/angular instead of a fork, which is why the deploy_aio job is failing.

[mgechev]

@sonukapoor thanks for the heads up.

[ngbot]

I see that you just added the action: merge label, but the following checks are still failing:
     status "ci/circleci: deploy_aio" is failing
     missing required labels: target: *
     status "pullapprove" is pending
     1 pending code review

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[AndrewKushnir]

Hi @mgechev, it looks like there is a conflict with the master branch after merging 5b33798. Could you please update your PR and resolve conflicts? Thank you.

[mgechev]

@AndrewKushnir done!

[AndrewKushnir]

Thanks @mgechev 👍

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}