fix(crio): properly link crictl config and add crictl to system PATH during CRI-O install

## Description

During provisioner-deployed K8s node setup, the crictl configuration is not properly established:

1. The crictl config file is not linked into the appropriate `/etc` location
2. The crictl config file does not have the correct CRI-O socket path
3. `crictl` is not included in the system shell PATH variable

This was discovered during troubleshooting a provisioner-deployed K8s node.

## Acceptance Criteria

- [ ] Ensure the crictl configuration file is properly linked/placed in the expected `/etc` location during CRI-O install
- [ ] Ensure the crictl config file contains the correct CRI-O socket path
- [ ] Ensure `crictl` is added to the system shell PATH variable
- [ ] Verify the fix works on a fresh provisioner-deployed K8s node
- [ ] Add unit/integration tests for the configuration setup