Rename requirements table to requirement_management_requirements
A follow-up from !30052 (e7f270f3, comment 329216530)
!30052 (merged) moved requirements
model under RequirementManagement
namespace, but didn't rename requirements
table because because as @tigerwnz pointed out it would cause downtime and issues during deployment. It would be better to keep table name consistent and figure out how to rename the table w/o downtime.
Edited by Jan Provaznik