Fixed phys_locations update API to remove error related to mismatching region name and ID

[srijeet0406]

This PR is not related to any issue. It fixes the case where a physical location could not be updated in api v5.0, due to a bug where regiona name and region ID do not match.

---

Which Traffic Control components are affected by this PR?

• Traffic Ops

What is the best way to verify this PR?

If the user uses TP (with version 5) to update a PhysLoc's Region, the update will fail with the message "region name and ID do not match" before this PR. This error should be fixed with this change.
It can also be recreated by calling the endpoint and changing just the ID (and not the name). In this case the API should use the ID instead of name.

If this is a bugfix, which Traffic Control versions contained the bug?

• master

PR submission checklist

• This PR has tests
• This PR has documentation
• This PR has a CHANGELOG.md entry
• This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

[codecov]

Codecov Report

Merging #7762 (6709a28) into master (82901de) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #7762      +/-   ##
============================================
- Coverage     31.90%   31.88%   -0.02%     
  Complexity       98       98              
============================================
  Files           712      712              
  Lines         81920    81907      -13     
  Branches        965      965              
============================================
- Hits          26134    26114      -20     
- Misses        53641    53642       +1     
- Partials       2145     2151       +6     

Flag	Coverage Δ
golib_unit	53.70% <ø> (+<0.01%)	⬆️
grove_unit	12.02% <ø> (ø)
t3c_unit	5.99% <ø> (ø)
traffic_monitor_unit	26.33% <ø> (ø)
traffic_ops_integration	69.38% <ø> (ø)
traffic_ops_unit	21.60% <ø> (-0.05%)	⬇️
traffic_portal_v2	74.38% <ø> (-0.02%)	⬇️
traffic_stats_unit	10.76% <ø> (ø)
unit_tests	29.18% <ø> (-0.03%)	⬇️
v3	57.79% <ø> (ø)
v4	79.18% <ø> (ø)
v5	78.49% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed	Coverage Δ
.../traffic_ops_golang/physlocation/phys_locations.go	10.32% <ø> (+0.30%)	⬆️

... and 3 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[shamrickus]

LGTM
Added test case and bug is fixed.