fix: Change dataset name affect data access role set to this dataset

[diegomedina248]

SUMMARY

When the user changes the name of a virtual dataset, any user that had specific access to said dataset will no longer be able to access it.

The issue is because the set_perm function is changing the table name but not the permission and view_model, thus, a new permission/view is created and the users keep pointing to the old one.

This PR ensures that, on name change, those records are also updated.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Before:

Screen.Recording.2022-06-30.at.18.18.17.mov

After:

new.mov

TESTING INSTRUCTIONS

1. Create a virtual dataset
2. Create a new role and grant access to the created dataset
3. Create a new user and assign the Gamma role, and the role created in 2.
4. Access the dataset list with that user
5. With the admin account, change the dataset table name
6. Ensure the user created in 3 can still see the dataset, now with the new name

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API