Fix for bug that prevents saving tab name changes in a tabbed report

[CWDamm-Kint]

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Description of Change

Two data-binds needed merging in the tabbed report htm file, which meant that the binding for the name field wasn't working properly when editing tabs.

Issues Solved

Closes #11617

Checklist

• I targeted one of these branches:
  • dev/8.0.x (under development): features, bugfixes not covered below
  • dev/7.6.x (main support): regressions, crashing bugs, security issues, major bugs in new features
  • dev/6.2.x (extended support): major security issues, data loss issues
• I added a changelog in arches/releases
• I submitted a PR to arches-docs (if appropriate)
• Unit tests pass locally with my changes
• I added tests that prove my fix is effective or that my feature works
• My test fails on the target branch

Accessibility Checklist

Developer Guide

Topic	Changed	Retested
Color contrast
Form fields
Headings
Links
Keyboard
Responsive Design
HTML validation
Screen reader

Ticket Background

• Sponsored by: Knowledge Integration
• Found by: @CWDamm-Kint @SDScandrettKint
• Tested by: @CWDamm-Kint
• Designed by: @CWDamm-Kint

Further comments

NA

[chiatt]

This does improve activation of the dirty state when a name is changed (although I still had to switch between tabs to get it to fire). However, it seems there is more to the problem than the dirty state. If a user saves their tab name changes, their edits are not committed to the database and the changes are lost on page refresh.

[chiatt]

This does improve activation of the dirty state when a name is changed (although I still had to switch between tabs to get it to fire). However, it seems there is more to the problem than the dirty state. If a user saves their tab name changes, their edits are not committed to the database and the changes are lost on page refresh.

@CWDamm-Kint You can disregard my last message. There was an issue with my local instances preventing the save. Your changes looks good. If you resolve the merge conflict, I can go ahead and approve this.