EPIC: prevent NRs from being used multiple times

1. There are a few tickets in this dashboard related to this. They need to be linked to this epic.

2. See this conversation and pull the requirements and proposed designs here.
https://teams.microsoft.com/l/message/19:cc93369433d341e7b5aa42b5ff78f7e0@thread.tacv2/1748628377620?tenantId=6fdb5200-3d0d-4a8a-b036-d3685e359adc&groupId=00bd6377-9feb-44be-bbc8-19c3752a67b2&parentMessageId=1748628377620&teamName=External%3A%20SBC%20REG%20Modernization&channelName=Entities%20-%20Olga&createdTime=1748628377620

Food for thought:
- should we only prevent filings from being submitted (to API) with an already-in-used NR?
- should we also prevent new filings from in-use NRs?
One proposal:
- [ ] Automatically mark the NR "In Use" the moment a Draft filing is created involving that NR.
- [ ] For every ulterior attempt to re-use that NR display the message: "In Use by account 12345"
- [ ] If the original Draft is deleted, the NR goes back into Approved state.
- [ ] If the original Draft is materialized into a filing, the NR goes back into Consumed state, making it impossible to be used again..