Consider simplify workspace - package [patch] table relation

[kayagokalp]

With #4086, workspaces will have [patch] table support and the current relation between workspace and package [patch] table is the following:

'If the workspace manifest file contains a [patch] table, a member package's manifest file cannot contain any [patch] declarations.'

@mitchmindtree stated rust's approach is a little bit simpler which is (https://github.com/FuelLabs/sway/pull/4086/files#r1163520745):

i.e. "If workspace exists, patch table must go in workspace manifest. Otherwise patch table can go in package manifest."

[cr-fuel]

cargo on rust will warn to the CLI. I will copy the same approach although it would be best to just error/panic and force the user to fix their mistake (move the patch to the workspace root)

This is cargo's output:

warning: patch for the non root package will be ignored, specify patch at the workspace root:
package:   /Users/cr-fuel/projects/sway/crates/types/Cargo.toml
workspace: /Users/cr-fuel/projects/sway/Cargo.toml
    Blocking waiting for file lock on package cache