Improving error specificity: ParaLocked instead of BadOrigin in ensure_root_para_or_owner

[ipapandinas]

Is there an existing issue?

• I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

• This is not a support question.

Description of bug

While attempting to deregister a parachain using the manager account, I encountered a BadOrigin error. Upon investigation, the issue was that the parachain was locked, and a ParaLocked error would have provided more clarity.

It seems that BadOrigin from ensure_parachain might be overriding other contextually relevant errors here, such as ParaLocked. Is this the intended behavior? If not, I can propose a fix to avoid this error overriding and improve the user experience.

Steps to reproduce

1. Deregister a locked parachain using the manager account.
2. Notice the BadOrigin error.