Do we really need ceph-salt grains?

(Relying on the pillar is more secure because only the master node can set it)

For ceph-salt minions targetting, we can use pillar:

```
salt -I ceph-salt:minions state.apply
```

instead of grain:

```
salt -G ceph-salt:member state.apply
```

So, apart from `ceph-salt:execution` grains that are set during execution for orchestration, do we really need any other `ceph-salt` grains?

(AFAIK, Suse Manager doesn't support grains)

Start by auditing where ceph-salt grains are defined and consumed, comparing those uses with pillar-based targeting. Check the Salt commands shown in the issue and distinguish execution-time grains from other grains. Done means documenting which grains are still required and identifying the affected configuration or targeting changes.

Written by the indexing model from the issue text.