[candidate_parameters] Users without permission to see candidate parameters are able to see the "button" to access it.

[racostas]

Describe the bug
Minor UI bug.
Users without permission to see candidate parameters are able to see the "button" to access it even if 403 is warranted in this case.

To Reproduce
Steps to reproduce the behavior (attach screenshots if applicable):

1. Logging into LORIS without having any of the candidate parameters permissions.
2. Go to MainMenu->Candidate->Access Profile and click in one of the Candidates.
   
3. The "Profile" information is shown and the button to access the candidate_parameters info is there even if will be always going to 403 error since the user don't have permissions to access it.
   
4. If the button is clicked
   

What did you expect to happen?
If the user don't have permission to access this info we should not even show the button to access it.

Browser Environment (please complete the following information):

• OS: MS Windows 11
• Browser: Chrome
• Version 133.0.6943.127 (Official Build) (64-bit)

Server Environment (if known):

• loris 27 demo official testing VM

[adamdaudrich]

I see that this button remains there when [all] candidate permissions are deselected.

[adamdaudrich]

@racostas what file is this button issue located in?

[adamdaudrich]

I am not sure that this is a [candidate_parameters] issue.

Because, by unchecking Permissions/
[ ] Access Profile: View/Create Candidates and Timepoints - Own Sites, the Candidate Info button disappears.

[ridz1208]

@adamdaudrich without removing the site access permission for the user, if you remove the candidate parameter permissions does the button show?

if yes, it should not so you can issue a fix for that.
if no, just send a screenshot here of the permissions and the "missing" button

[adamdaudrich]

Yes, the button shows with candidate_view and candidate_edit permissions deselected. So I will fix that

[adamdaudrich]

related PR is #9696

[ridz1208]

@adamdaudrich it's okai here but for future reference when you link a PR to an issue, the issue is automatically closed by github when the PR is merged. That's because sometimes the PR gets closed so the issue should not get lost in these cases.