Keep ipv6 brackets after updating port/user/password

[j178]

What do these changes do?

Keep ipv6 brackets after updating port/user/password

Are there changes in behavior for the user?

Related issue number

close #451

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• Add a new news fragment into the CHANGES folder
  • name it <issue_id>.<type> (e.g. 588.bugfix)
  • if you don't have an issue_id change it to the pr id after creating the PR
  • ensure type is one of the following:
    • .feature: Signifying a new feature.
    • .bugfix: Signifying a bug fix.
    • .doc: Signifying a documentation improvement.
    • .removal: Signifying a deprecation or removal of public API.
    • .misc: A ticket has been closed, but it is not of interest to users.
  • Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.

[codecov]

Codecov Report

Merging #452 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #452   +/-   ##
=======================================
  Coverage   99.25%   99.25%           
=======================================
  Files           2        2           
  Lines         671      671           
  Branches      154      154           
=======================================
  Hits          666      666           
  Misses          5        5           

Impacted Files	Coverage Δ
yarl/__init__.py	99.00% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9949de4...f12d2a0. Read the comment docs.

[asvetlov]

LGTM!