Fix for targets where DEVICE_SPI or DEVICE_INTERRUPTIN are defined but not both

[talorion]

Summary of changes

Fixed a missmatch in the guards in NanostackRfPhyAtmel.h and NanostackRfPhyAT86RF215.cpp
the problem is better described in #13299
basically when either DEVICE_SPI or DEVICE_INTERRUPTIN are defined but not both we running Into the problem that the guards in NanostackRfPhyAtmel.h do not match the ones in NanostackRfPhyAT86RF215.cpp
I added a guard in rfbits.h which checks if DEVICE_SPI is defined since the file clearly requires SPI.

Impact of changes

on some custom targets where DEVICE_SPI or DEVICE_INTERRUPTIN are defined but not both the build fails

Migration actions required

Documentation

None

Pull request type

[X] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[X] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

---

[talorion]

copy of #13471
i accedentally force pushed the master, re-created the PR with cleaner commit history

[ciarmcom]

@talorion, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

[0xc0170]

CI started

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs	Status
jenkins-ci/mbed-os-ci_unittests	✔️
jenkins-ci/mbed-os-ci_build-ARM	✔️
jenkins-ci/mbed-os-ci_build-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️
jenkins-ci/mbed-os-ci_dynamic-memory-usage	✔️
jenkins-ci/mbed-os-ci_cloud-client-pytest	✔️

[0xc0170]

@artokin can you review - the drivers changes to rf, should be also upstream?

[artokin]

LGTM, @JarkkoPaso , would you please check also?

[0xc0170]

Thank you @artokin @JarkkoPaso

[artokin]

@0xc0170 , changes will be backported to mbed-os-5.15 via https://github.com/ARMmbed/atmel-rf-driver repository