Fix unexpected_cfgs in the crates and add a troubleshooting note

[tguichaoua]

• Moves the unexpected_cfgs lint configration at the workspace level
• Inherits the workspace lints in all crates
• Add a notes about the "unexpected cfg condition name: sycamore_force_ssr" in the troubleshooting section of the docs.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.41%. Comparing base (b0aa222) to head (fad8af9).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #783   +/-   ##
=======================================
  Coverage   71.41%   71.41%           
=======================================
  Files          45       45           
  Lines        6658     6658           
=======================================
  Hits         4755     4755           
  Misses       1903     1903           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[lukechu10]

Thanks for the PR and sorry for taking so long to get to this. I'm happy to merge this for now but I don't quite like this solution long term as it introduces extra friction to get started with Sycamore.

It seems like the main problem is that certain macros expand to cfg(sycamore_force_ssr) which then triggers the warning. Think behavior was introduced in rust-lang/rust#132572

I think the best solution would be to not expand to cfg(sycamore_force_ssr) but rather to true or false depending on the flag. This way we do not get warnings in downstream crates.